Hi Christian, Also thanks for input, and sorry for wasting your time: it's probably a false-positive issue, to reject.
I went too quick and proceeded before reading the 2 troubleshooting commands you advised. But well, I think I did the same in a less precise manner: -- $ sudo ls -lah /etc/apparmor.d/local/usr.sbin.libvirtd ls: cannot access '/etc/apparmor.d/local/usr.sbin.libvirtd': No such file or directory $ sudo aptitude reinstall libvirt-daemon-system The following packages will be REINSTALLED: libvirt-daemon-system 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 80,7 kB of archives. After unpacking 0 B will be used. Get: 1 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libvirt-daemon-system amd64 4.0.0-1ubuntu8.3 [80,7 kB] Fetched 80,7 kB in 0s (162 kB/s) Preconfiguring packages ... (Reading database ... 198730 files and directories currently installed.) Preparing to unpack .../libvirt-daemon-system_4.0.0-1ubuntu8.3_amd64.deb ... Unpacking libvirt-daemon-system (4.0.0-1ubuntu8.3) over (4.0.0-1ubuntu8.3) ... Setting up libvirt-daemon-system (4.0.0-1ubuntu8.3) ... virtlockd.service is a disabled or a static unit, not starting it. virtlockd.socket is a disabled or a static unit, not starting it. Setting up libvirt-daemon dnsmasq configuration. Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.3) ... $ sudo ls -lah /etc/apparmor.d/local/usr.sbin.libvirtd -rw-r--r-- 1 root root 0 août 16 19:27 /etc/apparmor.d/local/usr.sbin.libvirtd $ -- Since the file was statically bundled in a repository package in 16.04.x LTS, I didn't think it could be a generated asset. Well, this would mean that: - The 'libvirt-daemon-system' package was installed when I started the upgrade process from 16.04.x LTS - It got updated/upgraded during the upgrade process, but not purged-then-installed (I'm not sure if the later option should have happened) What I can assert: - I used a libvirt PPA a year ago, to test newer libvirt features. I'm not on a critical instance. PPA: https://launchpad.net/~jacob/+archive/ubuntu/virtualisation . Those features ran well since then - Before upgrading to 18.04 LTS, a small-week ago, I purged the PPA packages + removed the PPA (both through the 'ppa-purge' command), then installed the related Ubuntu repository packages again, by reinstalling from the top: 'sudo aptitude reinstall qemu-kvm libvirt-bin', that fetched its dependencies as needed. This is probably where I screw up Ubuntu's defaults for libvirt, by mismanaging the PPA - Since I moved to 18.04 LTS, I rely only on Ubuntu's defaults (i.e. main/security/universe/multiverse) packages This probably narrows down to me not using APT properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786677 Title: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
