It is likely related to the kernel. I have another hypothesis around profile loads. What I think might be happening is an out of order load where the child is loaded first (this can happen due to parallel compiles etc), and then the parent is being replaced. It is just a hypothesis, but there were changes around the fs and apparmor policy locking since 6.15 because of refactoring in the fs.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2139664 Title: snap service cannot change apparmor hat To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2139664/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
