registry team mailing list archive

[komputes <484429@xxxxxxxxxxxxxxxxxx>]

** 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 that the disk is no longer usable giving this error.
+ Bringing the key to another computer works because the luks mapper point
+ is not unlocked and already present on that system.
  
  Steps to reproduce:
  1) Go into palimsest (disk utility) and create an encrypted partition on an external disk.
  2) Quit Palimsest
  3) Pull the USB stick
  4) Intert the USB stick
  
  Result:
  GNOME displays a dialog for the password. Once submitted, the following error comes up:
  Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
  
  This is due to the mapping being Opened when the disk is created, but
  never closed, which creates a conflict.
  
  Workaround:
  Do the following to resolve the conflict of the existing device i /dev/mapper.
  $ ls -al /dev/mapper
  (Identify the mount point for your drive, "sudo blkid" may help)
  $ sudo cryptsetup luksClose devkit-disks-luks-uuid-<uuid>-uid1000
  
  What is expected:
  Palimsest (Disk Utility) is expected to  "cryptsetup luksClose" the mapped device when finished creating the encrypted partition.
  
  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa
  CheckboxSystem: 099634613a96bc3665b92c4a813055e8
  Date: Tue Nov 17 15:37:09 2009
  DistroRelease: Ubuntu 9.10
  Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7
  ProcEnviron:
-  LANGUAGE=
-  PATH=(custom, user)
-  LANG=en_CA.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  PATH=(custom, user)
+  LANG=en_CA.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: cryptsetup
  Uname: Linux 2.6.31-12-generic i686

-- 
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.