[gutsy] [regression] LUKS automount fails

Bug #155020 reported by Fridtjof Busse
4
Affects Status Importance Assigned to Milestone
gnome-mount (Ubuntu)
New
Undecided
Unassigned

Bug Description

If you plug in an encrypted volume (LUKS), gutsy ask for the passphrase and opens the volume under /dev/mapper/luks_crypto_$id.
But rather than mounting the decrypted volume, gutsy does nothing, you have to mount the volume manually via commandline. It worked very well on feisty.
Nothing unusual in /var/log/daemon other than lots of "New device added" from HAL.

Revision history for this message
Peter Wainwright (prw) wrote :

Looks like Bug #148003.

IMHO, it's a race between udev and cryptsetup (libdevmapper).

I "fixed" it by removing /etc/udev/rules.d/65-dmsetup.rules.

This file seems to have been introduced by a recent Ubuntu patch. Presumably there was a good reason for it, but it causes havoc.

Revision history for this message
Thorsten Bonck (bonck-deactivatedaccount) wrote :

I'm able to reproduce this bug under hardy alpha 4.
Removal of /etc/udev/rules.d/65-dmsetup.rules could solve the problems of automount, but also could render your system unbootable after an initramfs-update (see: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/148003/comments/33)

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.