The STATUS messages are fine, and are just confirming that the apparmor profile was loaded/replaced.
That cache directory is created at package installation, and would only change if the python code changed. When the package is installed or upgraded, its post-installation scripts will trigger a regeneration of this cache. If the python code is changed locally, like by directly editing a file, the cache will no longer correspond to the code, and will auto-update. Or attempt to auto-update, at least. The systemd service applies the apparmor profile and won't allow that update to happen (which is correct). My guess is that at some point a local change was perhaps made to one of the python files, and that invalidated the cache. Or maybe the post-install script had failed before, and didn't update the cache files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107332 Title: AppArmor denied audit messages related to __pycache__ in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2107332/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
