encrypted /tmp partition doesn't mount during boot after update to lucid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After an upgrade from karmic to lucid (kubuntu) my luks-encrypted /tmp partition failes to mount during booting the system.
It then gives me the option to boot it manualy and then to continue with booting. The mounting of tmp works, but unfortunatly I'm not able to decrypt my ecrytptfs-encrypted home directory for some reason.
On the other hand, when I continue booting without mounting /tmp and then first login to a console (graphical login fails due to missing tmp-directory) and then mount tmp with sudo everything works fine.
Here is the relevant entry of my fstab:
/dev/mapper/tmp /tmp ext2 defaults 0 0
And this is what my cryptab looks like:
tmp /dev/disk/
I'm not sure if this bug is related to https:/
reassigned to cryptsetup package then