When mounting manually, the standard way is to "map" the encrypted drive or partition using "cryptsetup luksOpen", which automatically creates a mapper device in /dev/mapper/<chosen alias>. gnome-mount (or is HAL responsible for this?) seems to be doing it the same way, choosing an alias "luks_crypto_<uuid>". It seems that instead of mounting this device after it is created, gnome-mount tries to mount /dev/dm-0 for some reason. And for some reason, it only does this sometimes.
-- "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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
