Comment 38 for bug 372014

Problem remains in Lucid* -- and is in fact much more frequent now, practically filling the dmesg logs to the point where they're no longer useful. Tried the command mentioned above, ie:

  find $HOME/.Private -xdev -size 0c -exec ls '{}' \; | wc -l

Returned 0.

Errors are same as above:
...snip...
[35503.313160] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
[35803.356768] Valid eCryptfs headers not found in file header region or xattr region
[35803.356779] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
[36103.351551] Valid eCryptfs headers not found in file header region or xattr region
[36103.351562] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
[36403.328506] Valid eCryptfs headers not found in file header region or xattr region
[36403.328518] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
[36703.315417] Valid eCryptfs headers not found in file header region or xattr region
[36703.315428] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
...snip...

Hundreds of these messages over the course of a few hours. I'm really surprised this problem (which first started in Karmic, for my system at least) managed to make it into Lucid ... admittedly this was somewhat presumptuous of me, but I kind of thought this would be fixed before the LTS was released -- especially since the "encrypted home directory" is such a popular (and well-advertised) feature. Since upgrading to Lucid didn't fix the error, I guess I'm looking at a total reinstall (sans the ecryptfs stuff), moving my data out of my home folder and back in again, etc -- yikes.

And everything worked so well for > 1 year... only started up (for me, at least) in Q1 of 2010.

Not sure why the status was changed to invalid and the appropriate target (ecryptfs, ecryptfs-utils, etc) were replaced with "launchpad" earlier, but I'm reverting that with apologies in advance: but how exactly is this a "launchpad issue?"

*Linux 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux (Ubuntu Lucid 10.04 LTS)