Breaks policykit/systemctl commands when restarted
Bug #1540282 reported by
Unit 193
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
Fix Released
|
Low
|
Martin Pitt |
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.
Changed in dbus (Ubuntu): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
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.