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

Resolve permission errors for --install, --remove, and cpufreqctl.auto-cpufreq on Ubuntu 24.04 #762

Merged
merged 1 commit into from
Dec 1, 2024

Conversation

Uyonoh
Copy link
Contributor

@Uyonoh Uyonoh commented Aug 10, 2024

Add execution permissions to auto-cpufreq-install, auto-cpufreq-remove, and cpufreqctl.auto-cpufreq to enable installation and removal of daemon, as well as statistics (--stats).
The install shell does display Permission denied, but goes on as though it was something unimportant. However, the program is not installed properly and cannot be used effectively.

Screenshot from 2024-08-10 22-38-36
debug.log

@AdnanHodzic
Copy link
Owner

AdnanHodzic commented Aug 24, 2024

I nor anyone else has ever ran into this issue. So I'm not too eager to merge changes to files which auto-cpufreq doesn't edit and simply relies on.

I'm not sure what changed or your system that you needed these changes. Hence, instead of accepting the changes or closing the PR, I'll simply leave it be for some time, until I see someone else report that they had the same problem.

@Uyonoh
Copy link
Contributor Author

Uyonoh commented Aug 26, 2024

Alright, thanks

@Tuxman2
Copy link

Tuxman2 commented Nov 30, 2024

Hello,

same problem on Fedora 41 with tuned. Permission denied on auto-cpufreq-install. :-(

See my post.

@AdnanHodzic
Copy link
Owner

In that case let's merge this :)

@Uyonoh Thank you for your contribution, you will be credited for your work as part of future release.

@Tuxman2 let's continue the discussion in #797

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

Successfully merging this pull request may close these issues.

3 participants