udev and/or kernel crypto issues

Bug #434238 reported by Dennis Heinson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
Invalid
Medium
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned
udev (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Bad bad breakage since about a week ago. I chose "encrypt my home folder" in Karmic installer. An update about a week ago broke the whole thing. I am attaching a photo of the console output.

Please instruct me as to how fetch additional information should it be necessary.

Thank you!

Revision history for this message
Dennis Heinson (dheinson) wrote :
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Hmm, this doesn't look like an eCryptfs issue to me. What about it makes you think that it's eCryptfs-related?

I'm going to add linux and udev to the affected packages, as it looks like a bug introduced there, perhaps?

:-Dustin

Changed in ecryptfs:
status: New → Incomplete
importance: Undecided → Medium
summary: - [karmic] home folder encryption broken after recent update
+ udev and/or kernel crypto issues
Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

There's a lot of known bugs with booting encrypted filesystems in Karmic. Can you check to see if this bug is a duplicate of bug #421876 or #430496?

Revision history for this message
Dennis Heinson (dheinson) wrote :

Thank you for the reply Dustin and Gabe. No, this doesn't look similar to the descriptions in those bugs. Can you deduct anything from the screenshot? Can you give me instructions on how to further debug? It surprises me that noone else has encountered the same problem.
I can 100% reproduce on new installs.

Thanks
Dennis

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

Taking a closer look at your screenshot, it looks like the top warnings about "NAME=%k" are related to bug #430654, which should be fixed now. That should not affect your boot though, as they're just harmless warnings. The stuff at the bottom is the real source of the bug.

Revision history for this message
Dennis Heinson (dheinson) wrote :

Here is something I tried last night:

Download karmic daily build (live)
Put on USB stick
Clean install to free space on HDD
(select encrypted home)
boot

---> same error

So there must be something in an update that occurred at around last friday or so that breaks the whole thing. Perhaps a dev should try to reproduce in a VM?

Revision history for this message
Dennis Heinson (dheinson) wrote :
Revision history for this message
Dennis Heinson (dheinson) wrote :

Sorry for the multiple posts. This may relate too: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/206129

Revision history for this message
Dennis Heinson (dheinson) wrote :

Doesn't occur any longer. Please go ahead and close. Thank you.

Changed in udev (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu):
status: New → Invalid
Changed in ecryptfs:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.