Red Hat Bugzilla – Bug 460223
gnome-mount no longer automatically opens LUKS-encrypted partitions
Last modified: 2015-03-03 17:33:04 EST
Created attachment 315046 [details]
screenshot showing one locked device and one device luksOpen-ed manually
Description of problem:
In Fedora 10 alpha, LUKS-encrypted partitions are automatically opened as described in http://www.redhatmagazine.com/2008/07/31/whats-next-in-red-hat-enterprise-linux-part-2/
Now, however, while the partition is seen (in Nautilus' Computer view), I have to open it with 'cryptsetup luksOpen' manually. gnome-mount then automatically mount the device as previously, and correctly use the icon for an unlocked device.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Plug in a removable media with a LUKS-encrypted partition
As described above
User prompted for passphrase; LUKS partition opened and mounted
gnome-mount now silently fails on the command line (return value=1):
$ /usr/bin/gnome-mount -v -t --hal-udi || echo $?
not sure if this is related to the Fedora 8 bug,
which is still open.
Created attachment 315062 [details]
Does this patch help ?
Does not seem to help, no.
I can confirm that I don't see the dialog automatically pop up. And also that nothing happens when I click the icon in Nautilus. However it works fine using gnome-mount directly. Also, if set up via gnome-mount, "unmounting" (in quotes because this means first unmounting, then tearing down the cleartext device) works fine from Nautilus.
All this indicates it's a bug in gvfs, not gnome-mount (not surprising since gnome-mount haven't seen a lot of changes). So reassigning; I'll try to work on a fix.
I'm curious, Michel does
$ gnome-mount -v -b -d /dev/sdb2
(replace /dev/sdb2 with the crypted device, make sure
you haven't set up the cleartext device on the command line)
work for you?
Funnily enough, it was (In reply to comment #3)
> I can confirm that I don't see the dialog automatically pop up. And also that
> nothing happens when I click the icon in Nautilus. However it works fine using
> gnome-mount directly. Also, if set up via gnome-mount, "unmounting" (in quotes
> because this means first unmounting, then tearing down the cleartext device)
> works fine from Nautilus.
> All this indicates it's a bug in gvfs, not gnome-mount (not surprising since
> gnome-mount haven't seen a lot of changes). So reassigning; I'll try to work on
> a fix.
> I'm curious, Michel does
> $ gnome-mount -v -b -d /dev/sdb2
> (replace /dev/sdb2 with the crypted device, make sure
> you haven't set up the cleartext device on the command line)
> work for you?
Funnily enough, it was the exact same command (sdb1 = a vfat partition for livecd-iso-to-disk and to give customs officials something to play with).
I can confirm that it works, and unmounting tears down the LUKS mapping as well. Thanks!
I've committed a fix upstream for the problem that "mounting" luks volumes doesn't work
2008-08-28 David Zeuthen <email@example.com>
* monitor/proxy/gproxyvolume.c: (g_proxy_volume_mount):
(handle_volume_mount): Make sure we really read mount_flags and
use_mount_operation. Fixes RH bug 460223.
This fix will appear in the next gvfs release (on Monday) and will subsequently appear in Rawhide a day or two after.
The patch itself is here
if you need it fixed earlier.