Sorry, I meant dbus, i.e. /etc/init.d/dbus restart
and I'm aware that this does involve restarting a lot of stuff. I suspect you're right and this may not a bug specific to PolicyKit, but it is a valid bug. DBus services should be able to cope with being stopped and restarted like runlevel services are. Can you confirm whether you saw the same console-kit-daemon messages in /var/log/daemon.log ? I'll see if I can reproduce this just by restarting that specific bus service, then we could move it to the console-kit-daemon package. Interestingly it seems I can get the "unlock" button working again simply by logging out and back in again. It's odd that you say it broke NetworkManager for you - mine keeps on working. I'm using Kubuntu and the KDE applet though - maybe the GNOME one isn't as robust. It would be great if you could isolate some of your issues - e.g. does restarting the NetworkManager service break nm- applet? - and file them against the relevant packages. Obviously I didn't have any trouble logging out either - so perhaps KDM is more robust than GDM, or maybe it just doesn't use new dbus services. I'm not sure what switch user is doing on my computer though. Hmm. The login manager type issues you describe aren't too surprising if console- kit-daemon is not working. Thanks for looking at this -- PolicyKit fails after restarting dbus (restarting all dbus services) https://bugs.launchpad.net/bugs/231180 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
