Probably should turn this into a blog post at some point, but for now I just want to let everyone know the state of things.
If you didn't already know, there have been issues with Snaps where you have to manually re-run aa-lsm-hook
through usysconf
in order for snaps to work correctly. As it turns out, this was a symptom of a larger issue surrounding AppArmor needing to be updated. snapd
was expecting a newer version of AppArmor than we had in the repository, but AppArmor couldn't be updated until aa-lsm-hook
was fixed to use the new caching directory for AppArmor. snapd
was already using the new directory, so the cache was never getting updated for the older version of AppArmor we have been shipping. In order to fix all of this we needed to:
- Update AppArmor to a newer version (@livingsilver94)
- Fix / rewrite
aa-lsm-hook
to support the new AppArmor (me)
- Update
usysconf
to use the new aa-lsm-hook
(me/Josh)
- Coordinate updating all of this at the same time to make sure no one's systems break
I apologize for how long it has taken to get all of these things to line up, but I'm happy to say that as of today, these things have all been fixed in Unstable. Which means that (after the next sync) AppArmor will be working correctly again for everything in Solus and that you should no longer need to manually run usysconf
after installing or updating a Snap.
Testers welcome and I would like to thank everyone who have helped get this sorted. Cheers!