LUKS-encrypted thumb drive no longer auto-mounts in unity

[Nick Moffitt]

I used cryptsetup to create an encrypted ext4 partition on a thumb drive, and I tend to use that for sensitive data that I want to keep on my person at all times.

Normally when I plug it in, a dialog pops up asking me for the passphrase to the encrypted volume, which promptly gets mounted. Right now I'm not seeing any icons in my little side-bar, or even any attempt to do anything with it in my logs:

Feb 21 10:34:21 vezza kernel: [ 2112.800080] usb 2-1: new high-speed USB device number 6 using ehci_hcd
Feb 21 10:34:22 vezza kernel: [ 2113.329354] scsi9 : usb-storage 2-1:1.0
Feb 21 10:34:22 vezza mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Feb 21 10:34:22 vezza mtp-probe: bus: 2, device: 6 was not an MTP device
Feb 21 10:34:23 vezza kernel: [ 2114.330045] scsi 9:0:0:0: Direct-Access Lexar JD FireFly 1100 PQ: 0 ANSI: 0 CCS
Feb 21 10:34:23 vezza kernel: [ 2114.336605] sd 9:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
Feb 21 10:34:23 vezza kernel: [ 2114.337277] sd 9:0:0:0: Attached scsi generic sg1 type 0
Feb 21 10:34:23 vezza kernel: [ 2114.337844] sd 9:0:0:0: [sdb] Write Protect is off
Feb 21 10:34:23 vezza kernel: [ 2114.337853] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00
Feb 21 10:34:23 vezza kernel: [ 2114.339361] sd 9:0:0:0: [sdb] No Caching mode page present
Feb 21 10:34:23 vezza kernel: [ 2114.339369] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 10:34:23 vezza kernel: [ 2114.346360] sd 9:0:0:0: [sdb] No Caching mode page present
Feb 21 10:34:23 vezza kernel: [ 2114.346369] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 10:34:23 vezza kernel: [ 2114.347639] sdb: sdb1
Feb 21 10:34:23 vezza kernel: [ 2114.350072] sd 9:0:0:0: [sdb] No Caching mode page present
Feb 21 10:34:23 vezza kernel: [ 2114.350076] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Feb 21 10:34:23 vezza kernel: [ 2114.350079] sd 9:0:0:0: [sdb] Attached SCSI removable disk

...and that's all she wrote.

This is kind of important to me, as I need access to this data. It has worked in precise every time I rebooted/logged out until just this morning.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cryptsetup 2:1.1.3-4ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Tue Feb 21 10:29:02 2012
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: Upgraded to precise on 2012-02-21 (0 days ago)
crypttab: # <target name> <source device> <key file> <options>

[Nick Moffitt (nick-moffitt)]

I ran `cryptsetup luksOpen` from a shell, and successfully pulled data off this partition. This appears to be a bug in whatever gnome or unity daemon automates this process on drive insertion. Cryptsetup itself is not actually affected.

[Brian Murray (brian-murray)]

I was unable to recreate this and immediately after connecting the disk receivied a "Enter a password to unlock the volume" dialog.

[Brian Murray (brian-murray)]

12:42:57 - flash:[~] apt-cache policy udisks
udisks:
  Installed: 1.0.4-3
  Candidate: 1.0.4-3
  Version table:
 *** 1.0.4-3 0
        100 /var/lib/dpkg/status

[Nick Moffitt (nick-moffitt)]

After the latest reboot for updates, this did not reoccur.