Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

policy-kit installation wrong?! #43

Closed
steadfasterX opened this issue May 8, 2017 · 6 comments
Closed

policy-kit installation wrong?! #43

steadfasterX opened this issue May 8, 2017 · 6 comments

Comments

@steadfasterX
Copy link

In my case the following happened:

I installed the extension over extensions.gnome.org
Then after the extension gets enabled gnome asks multiple times for my password to execute cpufreqctl

The policy file gets installed correctly into:
/usr/share/polkit-1/actions/mko.cpupower.policy

but within that file I find the line:

<annotate key="org.freedesktop.policykit.exec.path">/home/tfi/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl</annotate>

which is either not correct or the installer missed to moved the cpufreqctl file from the directory src/.

I "fixed" it by modifying the path to:
<annotate key="org.freedesktop.policykit.exec.path">/home/tfi/.local/share/gnome-shell/extensions/[email protected]/src/cpufreqctl</annotate>

@steadfasterX
Copy link
Author

steadfasterX commented May 8, 2017

btw: /usr/share/polkit-1/actions/mko.cpupower.setcpufreq.policy contains the path to src/

hmm is the other one a left-over from a previous install?

@martin31821
Copy link
Member

this could be indeed a leftover from a previous version.
I will adapt the installer to remove old versions of the policy file...

@martin31821 martin31821 self-assigned this May 8, 2017
@martin31821 martin31821 added the bug label May 8, 2017
@Oliph
Copy link

Oliph commented Jul 26, 2017

I add the same issue and the solution given here solve the issue for me.

@superkartoffel
Copy link

superkartoffel commented Aug 8, 2017

I can confirm this issues. I also had a second policy, probably from a previous version and got asked to enter a password multiple times on each login and whenever I tried to use the extension.
Removing the second policy resolved the issue for me.

@eode
Copy link

eode commented Aug 30, 2017

Still broken. Still the same issue. Two polkit files, the older being mko.cpupower.policy, the newer being mko.cpupower.setcpufreq.policy. Deleting the older one fixes the issue.

@fin-ger
Copy link
Member

fin-ger commented Mar 31, 2020

This is being worked on in #107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants