You are not logged in.
Using Linux kernel 4.4.14 you won't be able to read the contend of a mounted ecryptfs directory. You can access a single file (as log as you know the exact name of the file) but trying to access directory results in an error "Wrong medium type"
Example:
[henry@localhost ~]$ uname -a
Linux localhost 4.4.14-1-lts #1 SMP Fri Jun 24 22:05:25 CEST 2016 i686 GNU/Linux
[henry@localhost ~]$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [5adab9dcafced280] into the user session keyring
[henry@localhost ~]$ echo foo >Private/bar
[henry@localhost ~]$ cat Private/bar
foo
[henry@localhost ~]$ ls Private/
ls: cannot open directory 'Private/': Wrong medium type
[henry@localhost ~]$ cat Private/b*
cat: 'Private/b*': No such file or directory
[henry@localhost ~]$ dmesg |tail -2
[ 602.159681] Error opening lower file for lower_dentry [0xf4a1a180] and lower_mnt [0xf5234010]; rc = [-124]
[ 602.162888] ecryptfs_open: Error attempting to initialize the lower file for the dentry with name [/]; rc = [-124]
See also
http://thread.gmane.org/gmane.comp.file … eneral/878
https://www.linuxquestions.org/questions/slackware-14/can't-access-ecryptfs-with-kernel-4-4-14-a-4175583163/
Offline
I've been subject to this, having my home directory (encrypted via ecryptfs) not being able to list files screwed up my whole Gnome session.
Downgrading to kernel 4.2.8.12 worked as a temporary solution, and I can confirm that upgrading to 4.6.3 works fine as well. As per the links the OP posted at the bottom, it seems that a patch is being backported at this very time.
Offline
Seems to be fixed as of 4.4.16-1-lts.
Logic clearly dictates that the needs of the many outweigh the needs of the few.
Online