are not present in the update done to Yakketty, but it seems they are needed.
By the way, those lines are also not present in /etc/apparmor.d/abstractions/base.
That file is included by the apparmor profiles generated for each snap (but not by ubuntu-core-launcher).
Please check this as well. This issue may affect more than just Snappy!
---
I'm on 16.04. Snappy was working fine for me, but this issue appeared a few days ago.
So maybe an update broke this?
I already commented in https:/ /bugs.launchpad .net/snappy/ +bug/1574556/ comments/ 5
I posted a log in there.
The fix (and workaround) is to add these lines to the end of the file /etc/apparmor. d/usr.bin. ubuntu- core-launcher, before the closing bracket ('}'):
# Workaround https:/ /launchpad. net/bugs/ 359338 until upstream handles /.ecryptfs/ */.Private/ r, /.ecryptfs/ */.Private/ ** mrixwlk,
# stacked filesystems generally.
# encrypted ~/.Private and old-style encrypted $HOME
owner @{HOME}/.Private/ r,
owner @{HOME}/.Private/** mrixwlk,
# new-style encrypted $HOME
owner @{HOMEDIRS}
owner @{HOMEDIRS}
And then reboot OR install the package "apparmor-utils" and run this command in a terminal:
sudo aa-enforce /etc/apparmor. d/usr.bin. ubuntu- core-launcher
I'm using this fix and Snappy is now working fine for me.
---
These lines:
owner @{HOME}/.Private/ r, /.ecryptfs/ */.Private/ r,
owner @{HOMEDIRS}
are not present in the update done to Yakketty, but it seems they are needed.
By the way, those lines are also not present in /etc/apparmor. d/abstractions/ base. core-launcher) .
That file is included by the apparmor profiles generated for each snap (but not by ubuntu-
Please check this as well. This issue may affect more than just Snappy!
---
I'm on 16.04. Snappy was working fine for me, but this issue appeared a few days ago.
So maybe an update broke this?