Comment 0 for bug 1871148

Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality.

Previously, when running any snap I would receive the following in the terminal:

---
cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: File exists
---