Mounting LUKS-enabled USB key always fails with "wrong passphrase" message

Bug #17493 reported by Martijn vdS
8
Affects Status Importance Assigned to Milestone
gnome-volume-manager (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

When I plug in my LUKS-enabled usb-disk, gnome-volume-manager asks me for a
passphrase.

When I type the passphrase, the device is not mounted, and this is in my
~/.xsession-errors:

manager.c/1033: Changed: /dev/sda1
manager.c/966: Added: /dev/sda1

** (gnome-volume-manager:7911): WARNING **: manager.c/698: failed to exec
/usr/bin/pmount-hal
Error: could not decrypt device (wrong passphrase?)

I setup LUKS like this:

cryptsetup luksFormat /dev/sda1
cryptsetup luksOpen /dev/sda1 usbdisk
mkfs.ext3 /dev/mapper/usbdisk
cryptsetup luksClose usbdisk
# then pull it out & plug it back in, and gnome-volume-manager asks me for a
passphrase.

Revision history for this message
Martin Pitt (pitti) wrote :

Just to confirm, the manual method

  pmount /dev/sda1

works?

If so, I'll build an extra debugging version soon. If you have time, maybe you
can do that yourself :-)

Revision history for this message
Martin Pitt (pitti) wrote :

This could be fixed in

 gnome-volume-manager (1.3.1-0ubuntu5) breezy; urgency=low
 .
   * Added debian/patches/07_dialogs_info.patch:
     - Hotplug popups are now information dialogs, not warnings.
     - Ubuntu #10651
   * Added debian/patches/08_photographss_typo.patch:
     - Fix typo "photographss" in src/manager.c and all translations.
   * debian/patches/06_pmount_crypt.patch:
     - Use g_child_watch_add() with a callback instead of waitpid(), since the
       latter does not work properly with g_spawn_async(). This could fix
       Ubuntu #11207.
     - If calling pmount-hal fails, and we have an encrypted device, show an
       error message box. (Ubuntu #11208)

Can you please try this version?

Revision history for this message
Martijn vdS (martijn) wrote :

Mounting works now, but unmounting gives me a dialog box with:

eject: unable to find or open device for: `/dev/mapper/_dev_sda1'

It's trying to eject the devicemapper file, while it should probably be ejecting
the underlying device. Otherwise, it's working great now!

Revision history for this message
Martin Pitt (pitti) wrote :

(In reply to comment #3)
> Mounting works now

Great, then I can close this bug. :-) Thanks for testing.

>, but unmounting gives me a dialog box with:
>
> eject: unable to find or open device for: `/dev/mapper/_dev_sda1'

Right, I know about this problem and I already have a half-working solution on
my hd. I need to think a bit more about it and will fix it soon.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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