On Tue, 13 Jul 2010 14:08:14 +0200 Milan Broz <mbroz@xxxxxxxxxx> wrote: > With new device-mapper udev rules are /dev/mapper/* symlinks > to basic device name /dev/dm-X. > (Change requested by udev upstream.) > > This change breaks temporary-cryptsetup workaround inside hal. > > With new dm-udev rules (uncluded since device-mapper 1.02.39) > there is DM_UDEV_DISABLE_OTHER_RULES_FLAG variable > which controls that scan should be ignored for this device > (it is set for all internal devices, including temporary cryptsetup, > internal parts of lvm devices etc.) > > Ignore device if this flag is set. > > See bugs > https://bugzilla.redhat.com/show_bug.cgi?id=613909 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586286 Perhaps this is a problem with how Xfce's automount implementation calls everything (although it worked fine prior to our move to udev-enabled LVM2 and newer cryptsetup (1.1.x)), but I still don't get an encrypted usb thumbdrive mounted when plugging it in after applying this patch and rebuilding hal. I get two separate dialog windows to enter the passphrase (the first appears, I enter the passphrase, and then the second appears), and after entering the passphrase for the second time, I get this: Failed to setup the encrypted volume. /dev/sdb is already setup? Just for grins and giggles, I tested an old mmc card, and it works as expected. I'm attaching a debug log created by running hald in verbose mode; any ideas on where to go from here? -RW
Attachment:
debug
Description: Binary data
