After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601797 - not able to store authentication
not able to store authentication
Status: RESOLVED NOTGNOME
Product: gnome-applets
Classification: Other
Component: cpufreq
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-13 12:40 UTC by Steven
Modified: 2010-03-16 07:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Steven 2009-11-13 12:40:19 UTC 
Hi,

in earlier versions i was able to store the authentication to change the cpu frequency.
Now this has gone, giving me the need to authenticate every time i want to change the frequency.

I'm using Ubuntu 9.10.

Regards
Comment 1 Carlos Garcia Campos 2009-11-15 11:33:47 UTC 
Looks like a problem with PolicyKit, does it happen also when trying to change the date/time, for instance?
Comment 2 Steven 2009-11-15 11:35:54 UTC 
Yep, can not store the authentication there either.
Comment 3 Carlos Garcia Campos 2009-11-15 11:39:38 UTC 
hmm, I would report it to launchpad then, since it looks like a PolicyKit or ubuntu issue. 

Thanks.
Comment 4 Martin Pitt 2010-03-16 07:04:27 UTC 
For the record, policykit is now designed to behave that way. What we'll do in Ubuntu is to allow the privilege to admins by default without asking, with a kind of "desktop-privileges" package (we already have something like that for udisks, but needs to be cleaned up a little).

Fedora has something similar, AFAIK.

So, no upstream bug here.