*** This bug is a duplicate of bug 148003 ***
https://bugs.launchpad.net/bugs/148003
This is in fact a duplicate of Bug #148003. See that bug for a
workaround.
** This bug has been marked a duplicate of bug 148003
mounting Luks encrypted USB-HDD does not work reliably
--
Can't mount a LU
Looks like it maybe related to 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
BTW: A reboot causes the system to prompt for password again.
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I've seen this bug as well. It occurs with firewire and usb drives. It
appears to assign a new device name each time the drive is plugged in. I
wonder how many times this would have to happen before something bigger
breaks? This bug is very frustrating since I'm using fully encrypted
disks througho
I also observed the following here:
When the device is plugged in, gnome-keyring asks me for the passphrase.
If I give the passphrase, the described bug occurs. However, if I deny
the question then gnome-mount itself also asks me for the passphrase. If
I then give the passphrase in this second dia
[0] nokile:~$ id
uid=1000(nikratio) gid=1000(nikratio)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(lpadmin),105(scanner),106(admin),1000(nikratio)
[0] nokile:~$ id hal
id: hal: No such user
[1] nokile:~$ id haldaemon
uid=116(haldaemon) gid=116(haldaem
The above logs have been created while plugging in a usb harddrive with
two unencrypted partitions, sdb1 and sdb3 that are mounted correctly,
and an encrypted partition sdb2 that is not mounted.
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this
** Attachment added: "udev.log"
http://launchpadlibrarian.net/10344162/udev.log
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/10344156/lshal.txt
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
** Attachment added: "gvm.log"
http://launchpadlibrarian.net/10344148/gvm.log
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/10344140/dmesg.txt
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
Attaching debugging files described in
https://wiki.ubuntu.com/DebuggingRemovableDevices
** Attachment added: "devices.txt"
http://launchpadlibrarian.net/10344136/devices.txt
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bugs/154679
You received this bug notificatio
Same problem here since the upgrade to gutsy. Luks volumes can only be
mounted the first time the device is connected, subsequent attempts fail
with "special device /dev/mapper/luks_crypto_(...) does not exist".
After manually creating the device mapper device, e.g. with
# cryptsetup luksOpen /de
I confirm that I am seeing a similar if not identical problem. I have
an external USB drive formatted with Luks and ext3. I'm running gutsy
on amd64 and have the update manager enabled.
** Changed in: gnome-volume-manager (Ubuntu)
Status: New => Confirmed
--
Can't mount a LUKS volume af
I should just add that if the device name for this device is changed
(for instance, if I mount another USB device first), then when I try to
mount it a second time, gnome will ask for the password and mount it
correctly.
--
Can't mount a LUKS volume after unmounting
https://bugs.launchpad.net/bug
15 matches
Mail list logo
