You are not logged in.
Hi there,
When I try to run polkitd, I get the following:
Entering main event loop
Lost the name org.freedesktop.PolicyKit1 - exiting
Shutting down
Exiting with code 0I've got polkit and gnome-polkit installed. I'm using smile with LXDE. This also happens when using lxdm though. Haven't tried gdm yet. This happens if I run polkitd as both root and my normal user, running it manually.
The reason I'm trying to run it manually, is I can see from 'ps -ef | grep polkit' that neither polkitd nor gnome-polkit is running, and thus I'm having permission issues in NetworkManager and some problems with pcmanfm which I think is related.
This is a brand new installation, after doing updates of all packages and installing lxde from scratch.
Anyone have any ideas where to start looking? I've found a source listing at http://policykit-1.sourcearchive.com/do … ource.html which shows where the message gets printed. It looks like for some reason, dbus is kicking off my polkitd, which makes me think permissions of some sort, or perhaps something else is already owning it? I've got no idea where to start looking though, polkit is new to me - on my previous Arch system (also using LXDE) this just worked.
Any ideas welcome.
Last edited by nicok (2012-09-03 17:38:53)
Offline
Is dbus running?
Offline
Thanks for the reply.
Dbus is running, I can see through ps -ef | grep dbus there are two dbus instances, one as "dbus" user and one as my normal user. Dbus is also added to DAEMONS in /etc/rc.conf
Unfortunately, I can't paste the output of the command as the other machine is not on the network at the moment ![]()
I've also tried the
exec dbus-launch startlxdein $HOME/.xinitrc but no dice yet.
Offline
Generally this means that DBus policy isn't allowing polkitd to own its proper bus name. I saw this recently when I tried Tom G's polkit 0.107. What happened in that case is that since a DBus policy file was changed, DBus noticed and immediately reloaded its config. However, that new polkit has its own user and group, which are referenced in that policy, but hadn't actually been created yet, as it's done by a post_install script on the polkit package. So DBus failed to parse the config properly, as it couldn't find the user the file referenced, and therefore didn't recognize it when polkitd tried to connect using it.
I saw messages like this in my logs:
Aug 07 18:53:54 amaranth dbus[357]: [system] Reloaded configuration
Aug 07 18:53:54 amaranth dbus-daemon[357]: Unknown username "polkitd" in message bus configuration fileThe solution was just to tell DBus to reload the config again, manually, once the user was there.
I also saw the same error once when I somehow managed to deleted or break permissions (I forget which) on polkit's own config files.
Offline