Unlock button in services is grayed out

[evdv]

Thanks a lot, you nailed it!
This avoided a lot of misery.

evdv

[youcanlinux]

Editing PolicyKit.conf didn't allow me to change services, but this did the trick...
$ su -c services-admin

[lns]

***** BIG FAT WARNING *****

DO NOT DO THIS IF YOU EXPECT ANY USER SECURITY!!! The "fix" described above (blindly putting <return result="yes"/> in /etc/PolicyKit/PolicyKit.conf) will allow ANY USER to start/stop services.

THIS IS BAD ON MULTI-USER SYSTEMS!! I am sure there is a cleaner fix for this. Please do not advocate bypassing security for functionality.

[lns]

To *safely* work around this issue, please do the following:

sudo polkit-action --set-defaults-any org.freedesktop.systemtoolsbackends.set auth_admin

This will require authentication of a user of the 'admin' group to use the "unlock" button of Services specifically instead of blindly granting authentication for EVERY policykit action for EVERY user without asking for ANY credentials.

Please note that you can use this command for other things as well, such as users-admin (which probably experiences the same issue if you're not logged onto the system console itself, such as if you're logged in via remote X, SSH, VNC, or an LTSP client). All you have to do is find the action identifier. For users-admin, it's "org.freedesktop.systemtoolsbackends.self.set" .

[highlander2]

Now I have upgraded to Karmic Koala and can't make "unlock " button enabled by editing /etc/PolicyKit/PolicKit.conf" simply because " Policy Kit" is deprecated in 9.10. How to enable "unlock" button by default ? It is so annoying to enter my password every time, and I don't need that level of security for my notebook.

[nik_nah]

I've tried adding
<return result="yes"/>

and...

sudo polkit-action --set-defaults-any org.freedesktop.systemtoolsbackends.self.set auth_admin


My "unlock" button in users-admin is still grey.

I'm logging in via vnc.

Thank god for command line.

[Bealer]

I've started getting this issue, and have tried all of the above suggestions but not had any luck.

I'm running a completely fresh install of 9.10. It's another frustrating regression bug that always seem to slip in after a release.