[Bug 1274833] Re: PolicyKit fails to allow the org.gnome.cpufreqselector action

2014-02-10 Thread Forest
I just tried this on today's daily trusty build. Running cpufreq-set --governor performance works fine as root, but still fails as a user in the adm and sudo groups. Exit code 218 again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1274833] Re: PolicyKit fails to allow the org.gnome.cpufreqselector action

2014-02-10 Thread Marc Deslauriers
cpufreq-set doesn't actually use the dbus service to change the cpu frequency, it tries to poke the sysfs directly, which you can only do as root. You need to use a tool that uses the org.gnome.cpufreqselector dbus api. ** Changed in: policykit (Ubuntu) Status: New = Invalid -- You

[Bug 1274833] Re: PolicyKit fails to allow the org.gnome.cpufreqselector action

2014-02-10 Thread Forest
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274833 Title: PolicyKit fails to allow the org.gnome.cpufreqselector action To manage notifications about this bug go to:

[Bug 1274833] Re: PolicyKit fails to allow the org.gnome.cpufreqselector action

2014-02-10 Thread Forest
Thanks for the pointer. Bummer. Can you point me toward some documentation on how this works and/or a command line tool that will change the cpu governor without sudo? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.