Public bug reported: I experienced this dbus-deamon-cannot-start-because-of-apparmor bug right at the first boot after installing (SHA1) `048b0b8925f1816b28e3527bfcd47d2842fa9f5e lubuntu-18.04-desktop- amd64.iso`. Please note that the installer has downloaded some packages files, the bug may not be in a package in the .iso. The bug made the first boot unsuccessful, it got stuck indefinitely at the boot logo.
After some debugging in recovery mode root shell, I observed that dbus- daemon was a zombie process, restarted by systemd every few minutes, and crashing within a second after each restart. I was able to get this error message: $ journalctl -u dbus -b -f | grep 'Failed to start message bus' Failed to start message bus: Error getting AppArmor context of bus: Permission denied I observed that all systemctl commands were timing out after 60 seconds, and systemd (strace -p 1) was repeatedly and in vain issuing a ppoll(2) system call for reading the dbus socket, and not making any progress with its other duties. More details here; https://askubuntu.com/q/1250238 ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1883865 Title: Lubuntu 18.04 doesn't boot because dbus-deamon crashes because of AppArmor Status in dbus package in Ubuntu: New Bug description: I experienced this dbus-deamon-cannot-start-because-of-apparmor bug right at the first boot after installing (SHA1) `048b0b8925f1816b28e3527bfcd47d2842fa9f5e lubuntu-18.04-desktop- amd64.iso`. Please note that the installer has downloaded some packages files, the bug may not be in a package in the .iso. The bug made the first boot unsuccessful, it got stuck indefinitely at the boot logo. After some debugging in recovery mode root shell, I observed that dbus-daemon was a zombie process, restarted by systemd every few minutes, and crashing within a second after each restart. I was able to get this error message: $ journalctl -u dbus -b -f | grep 'Failed to start message bus' Failed to start message bus: Error getting AppArmor context of bus: Permission denied I observed that all systemctl commands were timing out after 60 seconds, and systemd (strace -p 1) was repeatedly and in vain issuing a ppoll(2) system call for reading the dbus socket, and not making any progress with its other duties. More details here; https://askubuntu.com/q/1250238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1883865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
