This bug was fixed in the package dbus - 1.10.6-1ubuntu2
---------------
dbus (1.10.6-1ubuntu2) xenial; urgency=medium
* dont-stop-dbus.patch: Disallow manual (re)starts, as we don't (want to)
stop D-Bus on shutdown. (LP: #1540282)
* debian/rules: Don't start D-Bus on package installation, as that doesn't
work any more with the above. Instead, start dbus.socket in postinst,
which will then start D-Bus on demand after package installation.
-- Martin Pitt <martin.p...@ubuntu.com> Thu, 11 Feb 2016 12:58:02
+0100
** Changed in: dbus (Ubuntu)
Status: Fix Committed => Fix Released
--
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:
Fix Released
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
