GNOME Bugzilla – Bug 613220
polkit-gnome-manager not registered to polkitd
Last modified: 2010-03-18 12:54:08 UTC
This bug as reported in Launchpad against Ubuntu 10.04 [1]. PolicyKit version is 0.96 there. The GNOME agent is not registered to polkitd, meaning any action requiring authentication fails. Everything is alright on KDE. I asked the reporter to get the logs from the processes when they are manually started. Nothing interesting appears, except maybe that strange pointer in polkitd.log: ** (process:1985): DEBUG: 0x1194760 If you have ideas on what information can be useful, please ask, the reporter is very responsive! pang@barbaren:~$ sudo /usr/lib/policykit-1/polkitd > polkitd.log [see http://launchpadlibrarian.net/41204721/polkitd.log] -------- pang@barbaren:~$ /usr/lib/policykit-gnome/polkit-gnome-manager --no-exit (polkit-gnome-manager:1987): PolicyKitGnome-DEBUG: Starting PolicyKit GNOME session daemon version 0.9.2 --------- pang@barbaren:~$ pkcheck --allow-user-interaction --process 1987 --action-id org.freedesktop.systemtoolsbackends.set polkit\56retains_authorization_after_challenge=1 Authorization requires authentication but no agent is available. pang@barbaren:~$ pkcheck --allow-user-interaction --process 1987 --action-id org.freedesktop.systemtoolsbackends.set polkit\56retains_authorization_after_challenge=1 Authorization requires authentication but no agent is available. 1: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/540247
Err... I was confused polkit-gnome-authentication-agent-1 and polkit-gnome-manager. Forget about this, I'll come back when valuable information is available. ;-)
Sorry, that silly mistake made me believe there was a real bug. This was merely an autostart problem due to a disabled entry in ~/.config/autostart (whose origin may be weird, but definitely not a PK bug).