Hi Christian, This is a false-positive reopening of this issue indeed. Still, it may contain useful bits.
The error occurrence I forwarded is now solved, thanks to what you advised on a side-subject at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/comments/6 . When producing stacktrace in here ( https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/comments/28 ), the root cause was that I appended this snippet at the end of '/etc/apparmor.d/abstractions/libvirt-qemu': -- {dev,run}/shm/ rw, {dev,run}/shm/* rw, -- This was a mistake to add those rules, since I should have edited the existing ones (that you stated at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/comments/6 ). In the end, I kinda duplicated the '{dev,run}/shm' rules when producing the error. With the following diff + a reload of the AppArmor profile, the error vanished: -- $ sudo diff /etc/apparmor.d/abstractions/libvirt-qemu ~/.sys/bak-custom/etc/apparmor.d/abstractions/libvirt-qemu 56c56,57 < /{dev,run}/shm r, --- > /{dev,run}/shm rw, > /{dev,run}/shm/* rw, -- What I did was just moving the 2 lines initially appended to the files, in order to overwrite the existing rules. A few asserts when the error was produced: - None of 'sudo systemctl reload apparmor', 'sudo systemctl restart apparmor' or 'sudo systemctl status apparmor' (in sequence) returned or shew an error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
