Comment 15 for bug 725862

I'm getting the same bug with the release version of Natty (11.04) so with ecryptfs-utils 87-0ubuntu0.

I got the problem originally by logging out and logging back in without rebooting (which is what I usually do since I very rarely reboot/shutdown my machine).

Here's a terminal listing with most of the answers what were asked of the original poster:

username1@mybox:~$ ls Private/
[some private files]
username1@mybox:~$ ls -alF .ecryptfs/
total 24
drwx------ 2 username1 username1 4096 2009-04-23 15:22 ./
drwxr-xr-x 137 username1 username1 12288 2011-04-29 11:49 ../
-rw-r--r-- 1 username1 username1 0 2009-03-23 16:35 auto-mount
-rw-r--r-- 1 username1 username1 0 2009-03-23 16:35 auto-umount
-rw-r--r-- 1 username1 username1 17 2009-03-23 16:35 Private.sig
-r-------- 1 username1 username1 48 2009-03-23 16:35 wrapped-passphrase
-rw-r--r-- 1 username1 username1 0 2009-04-23 15:22 .wrapped-passphrase.recorded
username1@mybox:~$ keyctl list @u
2 keys in keyring:
899674517: --alswrv 1000 0 user: 31bb03a50a74ed60
979231033: --alswrv 1000 0 user: a637b5831fc648bc
username1@mybox:~$ ecryptfs-umount-private
username1@mybox:~$ keyctl list @u
1 key in keyring:
899674517: --alswrv 1000 0 user: 31bb03a50a74ed60
username1@mybox:~$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [31bb03a50a74ed60] into the user session keyring
keyctl_search: Required key not available
Perhaps try the interactive 'ecryptfs-mount-private'
username1@mybox:~$ keyctl list @u
1 key in keyring:
899674517: --alswrv 1000 0 user: 31bb03a50a74ed60
username1@mybox:~$ cat .ecryptfs/Private.sig
a637b5831fc648bc
username1@mybox:~$ ls Private/
Access-Your-Private-Data.desktop README.txt
username1@mybox:~$ keyctl clear @u
username1@mybox:~$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [a637b5831fc648bc] into the user session keyring
username1@mybox:~$ ls Private/
[some private files]

Calling "keyctl clear @u" before calling "ecryptfs-mount-private" allows the directory to be mounted correctly... but I can't really do that during boot-up. :)

Thanks.