-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Issue with auto-cpufreq-gtk when packaged as RPM #677
Comments
Yeah I installed the .rpm in a container and got the same result. |
I'm using an immutable OS - and I guess going a step farther, it's a spin of Silverblue with everything customized out of the box (https://github.com/jitcos/cabos), so I wasn't able to use the installer script in my build process unfortunately |
@m0ngr31 auto-cpufreq works fine, it's only auto-cpufreq-gtk that's causing the issue? Could you give us the output of: Also, have you seen #601 as it could be relating to the same issue. |
@AdnanHodzic yeah, regular I can't run the first command since |
If you manage to figure it out, please give it a try and contribute to the project and you will be credited for your work as part of future release. |
Fill out information requested in this template, without doing so issue will be ignored & closed!
Have you tried?
Error output:
System information:
Add/paste output of:
Also please be descriptive about the issue you're reporting, i.e: what you tried & what's the expected behaviour.
I'm trying to use auto-cpufreq on a Fedora Silverblue 39 setup. I was able to figure out making a spec file to create an RPM: https://copr-dist-git.fedorainfracloud.org/cgit/sweetbeans/cabos/auto-cpufreq.git/tree/auto-cpufreq.spec
And added the compiled package to my COPR repo: https://copr.fedorainfracloud.org/coprs/sweetbeans/cabos/package/auto-cpufreq
auto-cpufreq seems to run perfectly for me, but trying to run
auto-cpufreq-gtk
just crashes silently. I can't find logs or anything anywhere. What can I do to diagnose what is causing the crash?The text was updated successfully, but these errors were encountered: