Comment 3 for bug 231180
Revision history for this message
| Alan Jenkins (aj504) wrote Re: PolicyKit fails after restarting dbus (restarting all dbus services) | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Right. Manually killing and restarting console-kit-daemon is sufficient to trigger this problem. I don't have complete information, but I still believe this is a bug in PolicyKit as well as console-kit-daemon.
My educated guess is that when console-kit-daemon is restarted, it forgets who's logged in. The information IS available - because the "w" command is quite capable of telling me who's logged in without running a daemon. So from my point of view that's a fairly damning bug in console kit (because it suggests the authors ignored the existing login/logging mechanism).
My understanding of PolicyKit is even more vague. However, my expectation is that system administration GUIs such as users-admin should be as robust as possible. I can't immediately think of a realistic situation where this would be critical and you really don't want to reboot to get PolicyKit working after console-kit-daemon has crashed. Nevertheless, the thought doesn't make me feel warm and fuzzy.