I can confirm this on a freshly installed intrepid ibex. To reproduce: Plug in a fully encrypted disk, the password dialogue pops up. Enter password, the device mapper gets created, gnome mount rejects to mount the drive. Quote: Cannot mount volume.
Unable to mount the volume '[label]'. mount: special device /dev/dm-4 does not exist and DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. If mounted manually the message reads: ~$ gnome-mount -vbd /dev/mapper/luks_crypto_[...] gnome-mount 0.8 ** Message: Given device '/dev/mapper/luks_crypto_[...]' is not a volume or a drive. Might the way in which the luks volume is created on the disk affect the way it is regarded by gnome mount? E.g. encrypting /dev/sdb1 instead of /dev/sdb? Please let me know if I can help by supplying additional data. -- "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
