FYI, this is fixed in the snap-confine that is in xenial-proposed and so
it will hopefully be fixed for all 14.04 LTS users soon. In the meantime
if you don't want to install proposed packages, the workarounds listed
in this report continue to work. I'll list the complete workaround here:
1. make sure /etc/apparmor.d/usr.bin.ubuntu-core-launcher has:
owner @{HOME}/.Private/ r,
owner @{HOME}/.Private/** mrixwlk,
# new-style encrypted $HOME
owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,
owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
2. load the updated profile into the kernel with: sudo apparmor_parser
-r /etc/apparmor.d/usr.bin.ubuntu-core-launcher
Keep in mind if you switch back and forth from snap-confine in xenial-
proposed and ubuntu-core-launcher that is in the archive, you may have
to reapply the above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
directory. errmsg: Permission denied
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1592696/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
