[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-05-10 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (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.

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-05-10 Thread Launchpad Bug Tracker
[Expired for dbus (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu Focal) 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.

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-05-10 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.

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-05-10 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Focal) 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.

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-03-11 Thread Dan Streetman
Not sure why you have an ordering loop between sockets.target and dbus.socket, can you provide the output of: $ systemctl cat dbus.socket $ systemctl cat sockets.target $ systemctl list-dependencies sockets.target $ systemctl list-dependencies --reverse sockets.target $ systemctl

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-03-10 Thread Balint Reczey
** Also affects: dbus (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) 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

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-03-01 Thread Lars Kollstedt
** Description changed: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle

[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-03-01 Thread Lars Kollstedt
This affects dbus, but the last change that could probably have caused this was in systemd. ** Package changed: dbus (Ubuntu) => systemd (Ubuntu) ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu