Part of the problem is that while d/p/dont-stop-dbus.patch prevents dbus from being stopped, it doesn't prevent another one from starting, thus systemctl restart dbus.service will not stop the current one but will indeed launch a new instance.
-- 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/1540282 Title: Breaks policykit/systemctl commands when restarted Status in dbus package in Ubuntu: New Bug description: When dbus is restarted, lightdm and network-manager flake out like normal, but in addition to that `service` and `systemctl` commands fail with a policykit timeout error. This issue is not in Debian and when dbus is installed from Debian this specific issue goes away. While restarting dbus isn't a "supported" thing to do, the system breaking apart and requiring restart is certainly bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1540282/+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
