I am also getting this error, and like Eugene says, it seems to be dependent on the environment in which the mount command is executed.
I attempted to mount from inside a tmux session, and the mount failed. I detached from the tmux session, issued the very same mount command in a plain ssh terminal, and the mount succeeded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1377924 Title: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING) Status in “apparmor” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Opinion Status in “openssh” package in Ubuntu: Confirmed Bug description: This is a reincarnation of Bug #1234412. Looks like issue is not related to specific kernel versions. Currently I am observing two Trusty (14.04) machines, with very close configuration, running same kernel: 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64. One is able to mount without the problem but the other is refusing: $ mount -t ecryptfs sec sec Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel keyring. Did you build key retention support into your kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
