Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=574933.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This error is making using encrypted external USB harddrives completely
unusable for me. I see that error every time I try to use any (of two
completely different) devices after a few minutes, sometimes after a bit
longer.
There are suggestions on help pages to use "sudo dmsetup remove
I am having this problem using 15.10. May be related to trying to mount an
encrypted external harddisk after the computer was suspended.
6 years after this bug has been opened it is still affecting people.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
For what it's worth, I'm seeing this exact problem in 15.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes the following
This problem still exists in trusty.
after suspend / resume an external excrypted harddrive automaint fails
with this error.
How to solve this totally annoying behaviour?
Also I would like to know: how can I make the automount mechanism forget
the password?
--
You received this bug
BTW this error seems to be triggered by the password input mechanism -
when I save the luks password "forever", volume management will always
remount that enrypted device without trouble after resume.
The two other options ("forget immediately" and "forget when log out")
lead to the described
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: cryptsetup (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: udisks (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I still experience this problem in trusty when
1) mount encrypted USB disk
2) suspend
3) unplug USB disk
4) wake up
5) plug in USB disk
6) try to mount again and answer the password prompt
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Desktop
For the work-around: sudo cryptsetup luksClose luks-id works when
you close all shells and editors which were working on a file or path on
the LUKS-drive.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided = Medium
** Changed in: udisks (Ubuntu)
Importance: Undecided = Medium
** Changed in: cryptsetup (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: cryptsetup (Ubuntu Maverick)
Importance: Undecided = Medium
**
This bug still exists with at least Ubuntu 13.04 and Ubuntu 13.10.
** Tags added: raring saucy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in
** Changed in: cryptsetup (Ubuntu Maverick)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device
I can reproduce the behavior on Ubuntu 11.10 (Natty) 64bit with the
following steps:
1) connect a luks-encrypted external harddrive and mount it
2) disconnect the drive
3) connect the drive
4) try to mount the encrypted partition again (happens automatically by default
when inserted)
--
You
I created an excrypted sdcard with palimpset.
1) Plug in a LUKS encrypted disk
2) At the password prompt unlock it (Disk will mount and be displayed on the
desktop)
3) Suspend computer
4) Remove sdcard
5) On resume, no errors
6) Insert encrypted sdcard from step 4)
7) Prompted to enter password
just adding that #33 is on 11.10 64bit with gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes the following
ubuntu 11.10 64bit, system76 serval laptop.
dmesg output after plugging in sdcard, entering password, recieving error
** Attachment added: luks-error-dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605403/+files/luks-error-dmesg.txt
--
You received
ubuntu 11.10 64bit, system76 serval laptop.
udevadm output after plugging in sdcard, entering password, recieving error
** Attachment added: luks-error-udevadm-info-export-db.txt
ubuntu 11.10 64bit, system76 serval laptop.
dmesg output after pulling out sdcard
** Attachment added: luks-error-dmesg-post.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605406/+files/luks-error-dmesg-post.txt
--
You received this bug notification
ubuntu 11.10 64bit, system76 serval laptop.
udevadm output after pulling out sdcard
** Attachment added: luks-error-udevadm-info-export-db-post.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605407/+files/luks-error-udevadm-info-export-db-post.txt
--
You
ubuntu 11.10 64bit, system76 serval laptop.
udisk output after pulling out sdcard
** Attachment added: luks-error-udisk-dump-post.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605408/+files/luks-error-udisk-dump-post.txt
--
You received this bug
ubuntu 11.10 64bit, system76 serval laptop.
udisk dump output after plugging in sdcard, entering password, recieving error
** Attachment added: luks-error-udisk-dump.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605404/+files/luks-error-udisk-dump.txt
--
I can't reproduce this in oneiric. Can you please give the output of
dmesg, udisks --dump, and udevadm info --export-db after ripping
out the USB stick?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
I can reproduce this bug in oneiric beta2 after unsafe remove of
encrypted drive.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device
00git-fix-luks-forced-removal.patch does not apply to the lucid sources.
Will some kind soul please backport the patch so we can get an SRU for
lucid?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
** Changed in: cryptsetup (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
** Changed in: cryptsetup (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: udisks (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: cryptsetup (Ubuntu Maverick)
Status: New = Confirmed
--
You
** Changed in: udisks
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes the following error:
** Changed in: udisks
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes the following error:
komputes,
this sounds like a more general problem, though -- I bet you can also
reproduce this with normal unencrypted USB sticks. Anyway, I think it's
worth filing a new bug about it. I guess what happens is that nothing
checks the state of USB devices after resuming, and thus there is never
a
Mathieu's patch fixes the error message in most scenarios:
- Ejecting device from palimsest without locking
- Pulling out device without warning the OS (unsafe)
- Suspend, Resume
However I found that it did not work for me in the following scenario (received
same error):
- Suspend, Pull Out,
In fact, while sleeping, I pulled out the disk, on return, the disk is
still there, and I can copy stuff to disk for a while before it realizes
the disk is not there. When it realizes the disk is no longer available,
it gives the following error:
Method DriveEject with signature as on interface
Pushed to upstream git head, thanks Mathieu!
** Changed in: udisks (Ubuntu Maverick)
Status: In Progress = Fix Committed
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
Uploaded into maverick review queue.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you are a member of
This bug was fixed in the package udisks - 1.0.1+git20100614-3
---
udisks (1.0.1+git20100614-3) unstable; urgency=low
* Add 00git-fix-luks-forced-removal.patch: In the event of the forced
removal of a crypto device, use the luks_holder property since it is still
available
** Branch linked: lp:ubuntu/udisks
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you are a member of
** Branch unlinked: lp:~mathieu-tl/+junk/lp484429
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you
** Branch linked: lp:~mathieu-tl/ubuntu/maverick/udisks/lp484429
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification
** Changed in: gnome-disk-utility (Ubuntu Maverick)
Status: Confirmed = Invalid
** Changed in: gnome-disk-utility (Ubuntu Lucid)
Status: New = Invalid
** Changed in: udisks (Ubuntu Maverick)
Status: New = In Progress
** Changed in: udisks (Ubuntu Maverick)
Assignee:
** Branch linked: lp:~mathieu-tl/+junk/lp484429
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you are
I can't reproduce this issue on my system unless I forcibly remove the
device (or suspend as commented by komputes), on the other hand, it
happens as well in nautilus, which leads me to believe the issue lies in
udisks rather than cryptsetup or elsewhere.
I can also see that udisks doesn't seem
In the initial description I had mentioned that disk utility does not
lock the drive after creating it.
I have just discovered another way to get this error:
1) Plug in a LUKS encrypted disk
2) At the password prompt unlock it (Disk will mount and be displayed on the
desktop)
3) Suspend computer
After discussing this with other users we feel that this issue could be
corrected in cryptsetup, or al least the graphical front end for it.
There is no graphical frontend that's part of cryptsetup.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup
so based on comment #12, the problem is either with gnome-disk-utility
or not fixed in the latest cryptsetup. Will target to lucid and
maverick, but still needs investigation into finding the right solution.
** Also affects: cryptsetup (Ubuntu Maverick)
Importance: Undecided
Status:
** Changed in: gnome-disk-utility (Ubuntu Lucid)
Importance: Undecided = Medium
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received
I beleive that one solution would be to have palimpsest lock the
encrypted drive after creating it. This way it could be ejected any
number of ways (palimpsest, nautilus, etc...) without the mapper point
still existing.
--
Plugging in a LUKS device causes the following error: Error unlocking
** Description changed:
Binary package hint: cryptsetup
+
+ When creating an encrypted drive in Palimsest (Disk Utility), the
+ application does not lock the disk when finished creating the encrypted
+ partition. Failing to lock the drive manually without ejecting will give
+ the appearance
** Description changed:
Binary package hint: cryptsetup
When creating an encrypted drive in Palimsest (Disk Utility), the
application does not lock the disk when finished creating the encrypted
partition. Failing to lock the drive manually without ejecting will give
the appearance
** Also affects: cryptsetup (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574126
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #574933
https://bugzilla.redhat.com/show_bug.cgi?id=574933
** Also affects: udisks (Fedora) via
Ubuntu Maverick Alpha 2
cryptsetup 1.1.2
Problem still exists.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification
Does anyone have a current workaround? None posted here work. This bug
should be marked criticial as it makes encrypted drives unusable on
Ubuntu.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device
cryptsetup 1.1.2 has been merged into maverick - can anyone confirm this
is fixed there?
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You
It appears that this may be fixed in the upstream cryptsetup
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574126
** Bug watch added: Debian Bug tracker #574126
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574126
--
Plugging in a LUKS device causes the following error: Error
I got the same problem on Lucid.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification because you are a member of
unsatisfactory workaround to do the whole thing manually.
NOTE: assumes that your external LUKS encrypted drive is mounted as
/dev/sdb1 and the device name in /dev/mapper is wdcrypt. Change these
for your own situation.
Create 2 scripts - mount-luks and unmount-luks (or umount-luks if you
are a
I just has the same issue using a LUKS encrypted USB drive (created in
Karmic) on a Lucid beta LiveCD session.
Unfortunately the workaround in the description no longer works for me.
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit
$ sudo cryptsetup luksClose
devkit-disks-luks-uuid-35df8717-0b13-45e6-9cfc-71d2cad4fd4d-uid1000
Command failed: Device busy
(Have tried this when the drive was unmounted)
$ sudo cryptsetup luksClose
devkit-disks-luks-uuid-35df8717-0b13-45e6-9cfc-71d2cad4fd4d-uid1000
Command failed
--
Plugging
The problem is only partially solved by making Disk Utility close the
luks device.
In fact all other situations in which a device is not closed correctly also
lead to this error.
I use an encrypted external harddrive. Whenever I shutdown the drive before
unmounting or suspend the pc, then
** Changed in: gnome-disk-utility (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: gnome-disk-utility (Ubuntu)
Status: Fix Released = Confirmed
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command
** Changed in: cryptsetup (Ubuntu)
Status: New = Invalid
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You received this bug notification
Setting to Confirmed, Medium.
From : https://wiki.ubuntu.com/Bugs/Importance
Medium: most bugs are of medium importance, examples are:
* A bug that has a moderate impact on a core application.
* A bug that has a severe impact on a non-core application.
* A problem with a non-essential
61 matches
Mail list logo
