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 to figure out which underlying cleartext LUKS device to
teardown, instead of scanning through all available devices (because the
cleartext device already has had its properties cleaned up). Many thanks
to Mathieu Trudel for the patch! Patch cherrypicked from upstream git
trunk. (LP: #484429)
-- Martin Pitt <[email protected]> Mon, 27 Sep 2010 18:56:00 +0200
** Changed in: udisks (Ubuntu Maverick)
Status: Fix Committed => Fix Released
--
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 Registry
Administrators, which is the registrant for Debian.
_______________________________________________
Mailing list: https://launchpad.net/~registry
Post to : [email protected]
Unsubscribe : https://launchpad.net/~registry
More help : https://help.launchpad.net/ListHelp
