Thanks, that might or might not be the reason for libvirt to behave differently and thereby trigger this. To see if it is that or anything else in your system, would it be easy or hard to reboot into the matching stock Ubuntu kernel and see if it emits the same? If it does, it isn't the kernel and we need to look further into what you do to trigger this (as I might have mentioned, when adding the allowance for anything to the profile we want to explain for which action/config we do so).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881969 Title: apparmor profile for libvirtd/libvirt-daemon needs fixing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1881969/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
