I further investigated this issue and found out the following: Whenever it works, the hal entry for the unlocked device, which should get mounted, contains the following line: block.device = '/dev/mapper/luks_crypto_fb656bfe-460b-4437-97d6-93bb6e9e66c4' (string)
Whenever it doesn't work, this line reads: block.device = '/dev/dm-4' (string) So this is the reason, the device cannot be mounted by gnome-mount. How are these entries created? During this conversation (http://lists.freedesktop.org/archives/hal/2008-April/011440.html) a race condition is described, which could cause hal to pickup on the dm-4 device and not notice the change after it has been unlocked. Could this be the case here? -- "special device /dev/dm-0 does not exist" when mounting an encrypted drive https://bugs.launchpad.net/bugs/296750 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
