Starting polkit goes fine:
tris...@tinygod4:~$ sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
[sudo] password for tristan:
Registering null backend at priority -10
Using authority class PolkitBackendLocalAuthority
** (process:10436): DEBUG: Added authentication agent for session
So you've found the info better than I did! I reckon you did not issue
this command through VNC? In that case, that would make things trickier.
As I suspected, there's something wrong with ConsoleKit, which should at
least have considered you as local for my tricks to work. You may get
more
Correct, the problem occurred before ever opening users-admin. I agree
with moving the bug after the remaining rights issue is resolved.
Terminal log below. The account having the problem is tristan. The
account that didn't experience problems is kateryna. Note though that
the kateryna account
OK, so it seems there's something strange with PolicyKit. What does 'ps ax |
grep polkit' reports? Please also run
pkcheck --action-id org.freedesktop.systemtoolsbackends.set --process `pidof
users-admin` -u
just after having started users-amin.
What does this command reports:
pkaction
tris...@tinygod4:~$ ps ax | grep polkit
2634 ?S 0:00
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
2655 ?S 0:00 /usr/lib/policykit-1/polkitd
6779 ?S 0:00
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
6893 pts/1S+
Thanks! Seems that PolicyKit is running correctly. Does
sudo killall polkitd; sudo /usr/lib/policykit-1/polkitd
report any error?
It may be that you're not detected as an active user, which could come from a
ConsoleKit problem. Then, connecting via VNC would actually matter, if there's
a bug in
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35332482/Dependencies.txt
--
User account lost permissions after Karmic upgrade, breaking all audio
https://bugs.launchpad.net/bugs/477832
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks for this detailed report. To make it completely clear, you
experienced these problems after upgrade and before running users-admin,
so that it cannot be the culprit? I'm asking that because it may also
have led to that situation, it's a problem we've already seen.
About the admin rights
