Ubuntu
gnome-mount package

Gnome-mount will only mount encrypted partitions and not drives created with cryptsetup/luks

Bug #117011 reported by Darren Albers
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-mount
Won't Fix
Medium
gnome-mount (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-mount

Please describe the problem:
When I create a luks encrypted drive, for example /dev/sdc I cannot mount it
via gnome-mount but it does mount via pmount and by hand (cryptsetup luksOpen
etc...) Gnome-mount evidently opens the luks encrypted container since I see
the mapper created however it is not mounted. The only error I see is an
unknown partition message when tailing /var/log/messages.

Gnome-mount DOES work when I mount an encrypted partition (/dev/sdc1) even if
that partition is of the whole drive.

This has only been tested on USB drives.

Steps to reproduce:
1. Use cryptsetup to create a luks encrypted volume on an entire usb drive
2. insert the drive
3. After entering the password see that the mapper device is created but not
mounted

Actual results:
The mapper device is created but not mounted

Expected results:
I would expect the drive to be mounted

Does this happen every time?
yes

Bug Watch Updater (bug-watch-updater)
Changed in gnome-mount:
status: Unknown → Unconfirmed
Revision history for this message
Basilio Kublik (sourcercito) wrote :

i just follow the steps:

1.- insert a usb drive with empty partition table
2.- losetup /dev/loop0 /dev/sda
3.- cryptsetup luksFormat /dev/loop0
4.- cryptsetup luksOpen /dev/loop0 Hipod
5.- mkfs.vfat -n Hipod /dev/mapper/Hipod
6.- cryptsetup luksClose /dev/mapper/Hipod
7.- losetup -d /dev/loop0
8.- detach the usb drive from the usb port and reattach it

after reattach the usb drive, pops up a gnome-keyring dialog asking for password, i enter the password, and nothing happens, manually mounting it, works fine.

if i follow the same steps, but instead an empty partition, i do it with let's say one partition, and work with that instead of the whole disk, all works fine automagically.

so i'm confirming this bug.

Changed in gnome-mount:
assignee: nobody → desktop-bugs
status: New → Confirmed
Revision history for this message
Peter Wainwright (prw) wrote :

I suspect this is also related to bug #148003...

Basilio Kublik (sourcercito)
Changed in gnome-mount:
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Martin Knudsen (brainwashed) wrote :

I can confirm this bug. After formatting my new usb-disk this way, everytime I plug it in it gets "decrypted", but I have to mount it manually via 'mount /dev/mapper/luks_123deviceid123 /media/mountpoint'

Revision history for this message
Gabriel Wolf (ecrug) wrote :

Here is a related problem.

When i click in nautilus on the cryptsetup/luks usb-drive (called 219gb-drive) it disappears.
i have to luksOpen it and mount it manualy, further - i can't delete the (once typed in) key from the
key-ring.

help.

Revision history for this message
Alexander Krivács Schrøder (alexschrod) wrote :

I can confirm this bug on my system as well. I have the whole disk encrypted instead of a partition (say /dev/sdb instead of /dev/sdb1) and although the password box shows up, nothing happens when I enter it. If I attempt accessing the disk again, I'm once again asked for the password. The only way around this problem is to manually cryptsetup and mount the disk.

Revision history for this message
BjornW (bjornw) wrote :

I would like to confirm this bug as well. I have the same issues as Alexander Krivács Schrøder. Can somebody tell me why this bug has a low priority?

Revision history for this message
Roy Sindre Norangshol (norangshol) wrote :

Confirmed, had to setup a partition (so drive has a valid partition table) on my usb pen drive to get auto mounting to work.

Revision history for this message
Alexander Krivács Schrøder (alexschrod) wrote :

A whole year later, and this is still not fixed. I would just switch from using the whole drive to a partition that fills the whole drive, it's just that the drive is 500 GiB, and more or less full, and I don't have room to move the stuff around to fix this problem that way. Why does gnome-mount (or hal, or whatever the culprit) have so much trouble mounting an encrypted drive? The password is asked for, the /dev/mapper/luks_* block file is created, it's just not being mounted.

Revision history for this message
Sébastien Pierre (sebastien-type-z) wrote :

Same thing here. I'm pasting what I pasted for bug#88213

1 - Plug dmcrypt-encrypted USB external HD in
2 - luks_crypto_69d35537-7865-4698-84c5-04283f517fbc appears in /dev/mapper
3 - "Encrypted data" volume appears in my Nautilus "Workplace" (Poste de travail in French)
4 - I double click on "Encrypted data"

Problem: I get a dialog saying

"Error org.freedesktop.Hal.Device.Volume.Crypto.SetupError
/dev/sdb is already setup?"

Then about 10 seconds later, I get this message:

"DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

To get it mounted properly, I have to (manually) do:

sudo mount /dev/mapperluks_crypto_69d35537-7865-4698-84c5-04283f517fbc /media/blackvault

Revision history for this message
Samuli Seppänen (samuli-seppanen) wrote :

I can confirm that this bug still exists on Ubuntu 9.04. This is not Ubuntu-specific, as I've had the exact same problem in Debian (a while after Etch's release) and in Gentoo.

Revision history for this message
Eric (eric-anderson) wrote :

Oddly, sometimes I get a failure and sometimes a success, with the exact same hardware and software. I'm posting a trace of each in the hope that it will shed some light on this for someone.

Success:

eanderso@eric-laptop:~/tmp$ gnome-mount -dvtb /dev/sdb3
gnome-mount 0.8
** (gnome-mount:15840): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d'
Enter password to unlock encrypted data for /dev/sdb3:
** (gnome-mount:15840): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d for crypto
Setup clear-text device for /dev/sdb3.
** (gnome-mount:15840): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d..
** (gnome-mount:15840): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_part_1_size_0
** (gnome-mount:15840): DEBUG: In crypto_setup_device_removed for /org/freedesktop/Hal/devices/volume_part_1_size_0
** (gnome-mount:15840): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5
** (gnome-mount:15840): DEBUG: /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 is backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d - will mount
Clear text device is /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d. Mounting.
** (gnome-mount:15840): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5
** (gnome-mount:15840): DEBUG: read mount point 'usb_crypto' from gconf string key '/system/storage/volumes/_org_freedesktop_Hal_devices_volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5/mount_point'
** (gnome-mount:15840): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 with mount_point='usb_crypto', fstype='', num_options=0
Mounted /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d at "/media/usb_crypto"
eanderso@eric-laptop:~/tmp$

Failure:

eanderso@eric-laptop:~/tmp$ gnome-mount -dvtb /dev/sdb3
gnome-mount 0.8
** (gnome-mount:15769): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d'
Enter password to unlock encrypted data for /dev/sdb3:
** (gnome-mount:15769): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d for crypto
Setup clear-text device for /dev/sdb3.
** (gnome-mount:15769): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d..
** (gnome-mount:15769): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_part_1_size_0
** (gnome-mount:15769): DEBUG: /org/freedesktop/Hal/devices/volume_part_1_size_0 is backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d - will mount
Clear text device is /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d. Mounting.
** Message: /org/freedesktop/Hal/devices/volume_part_1_size_0 does not have a mountable filesystem

Bug Watch Updater (bug-watch-updater)
Changed in gnome-mount:
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in gnome-mount:
status: New → Won't Fix
Revision history for this message
Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in gnome-mount (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.