[Touch-packages] [Bug 1883865] Re: Lubuntu 18.04 doesn't boot because dbus-deamon crashes because of AppArmor

2020-08-16 Thread Launchpad Bug Tracker
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: dbus (Ubuntu)
   Status: Incomplete => Expired

-- 
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:
  Expired

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


[Touch-packages] [Bug 1883865] Re: Lubuntu 18.04 doesn't boot because dbus-deamon crashes because of AppArmor

2020-06-17 Thread Chris Guiver
I did a QA-test install of Lubuntu 18.04.5 (daily), of course I only had
a tiny fraction of packages (14) to upgrade, I had no issues.

-- 
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:
  Incomplete

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


[Touch-packages] [Bug 1883865] Re: Lubuntu 18.04 doesn't boot because dbus-deamon crashes because of AppArmor

2020-06-17 Thread pts
Since than I don't have a Lubuntu 18.04 system anymore, so I'm not able
to run `apport-collect 1883865', and I'm unable to assist debugging this
any further. You may reproduce the bug by installing Lubuntu 18.04 using
the .iso I mentioned above.

Please note that regular Ubuntu 18.04 is not affected, I was able to
install and run it without any issues. The Lubuntu desktop environment
on a regular Ubuntu 18.04 is not affected either. What _is_ affected:
dbus + AppArmor after installing Lubuntu 18.04 using the .iso I
mentioned above.

-- 
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:
  Incomplete

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


[Touch-packages] [Bug 1883865] Re: Lubuntu 18.04 doesn't boot because dbus-deamon crashes because of AppArmor

2020-06-17 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1883865

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: dbus (Ubuntu)
   Status: New => Incomplete

-- 
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:
  Incomplete

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