reassign 467200 udev,cryptsetup,hal thanks More info about this accursed bug. ;)
Forget the udev rules, it seems I misinterpreted what upstream meant. What really happens is that cryptsetup (as part of the luksOpen operation) creates a 'temporary-cryptsetup-$pid' device mapping. There is a race between udev sending out notifies for this device, and cryptsetup destroying it again; if HAL sees the temporary device then it won't pick up on the real device once it has been created. It seems that HAL has had a workaround committed <http://gitweb.freedesktop.org/?p=hal.git;a=blobdiff;h=266453b26ddef29fbb3e378c497f280d53085bc7;hp=d28792e51d1bab04214f900ec2bc7cc60b8e26a2;hb=0f2dfc66d1f92aaf464adadeaf327d5a31e0ebcb;f=hald/linux/osspec.c> but it does not work; hotplug_event->sysfs.device_file is "/dev/dm-2" and not a string starting with "/dev/mapper/temporary-cryptsetup-". So the problem is lower down in the stack than GNOME; I guess udev, hal and cryptsetup need to co-operate in order to prevent this from happening. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
