[Bug 62751] Re: Upstart doesn't activate luks volumes (also non luks) in cryptsetup

[Curtis Hovey]

** No longer affects: null

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/62751

Title:
  Upstart doesn't activate luks volumes (also non luks) in cryptsetup

Status in “cryptsetup” package in Ubuntu:
  Fix Released
Status in “loop-aes-utils” package in Ubuntu:
  Invalid
Status in “usplash” package in Ubuntu:
  Invalid

Bug description:
  My laptop's home is a LUKS encrypted volume that's listed in crypttab
  to be mapped to /dev/mapper/home which worked wonderfully in dapper
  (i.e. boot interrupted, asked for pw, continued), in edgy however boot
  freezes, after a while the splash goes away, I get to single user and
  fsck complains about not being able to check /dev/mapper/home (which
  is in fstab) because the LUKS volume was not activated. Activating the
  volume by hand lets the boot process continue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/62751/+subscriptions