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

Feature suggestion: Complete uninstallation #58

Closed
jebeld17 opened this issue Feb 16, 2018 · 9 comments
Closed

Feature suggestion: Complete uninstallation #58

jebeld17 opened this issue Feb 16, 2018 · 9 comments
Assignees

Comments

@jebeld17
Copy link

Please add a 'Completely Uninstall' option to the CPU Power Manager applet that completely reverses any changes the applet may have done to the user's computer including remove and reverse the scripts installed by the applet to work properly.

This gives users peace of mind that in case the applet does not work for their needs, they can still reverse any changes, more than likely, that may have incurred.

@GXGOW
Copy link

GXGOW commented Feb 21, 2018

According to #48, you only have to remove one file. It would be helpful to put that in the README though.

@martin31821
Copy link
Member

I'll put it in the readme.

@jebeld17
Copy link
Author

What about to undo the changes?

@jlemonde
Copy link

Even if I removed this one file (or executing ./install.sh uninstall), I am not sure if the last state of the extension is not kept forever.

What is the default behaviour of the CPU, for sure?
min:0%, max:100%, boost enabled?

@kiview
Copy link

kiview commented Jan 3, 2019

I assume it would be reset after restart, not sure though?

@micklynch
Copy link

Can anyone confirm how do, and what happens if, I uninstall?

@martin31821
Copy link
Member

pstate is resetted after every boot to full frequency range and enabled turbo boost.

@berkiyo
Copy link

berkiyo commented Sep 10, 2019

Can anyone confirm how do, and what happens if, I uninstall?

@micklynch Simply uninstall the extension from extensions.gnome.org and reboot. I can confirm that upon rebooting, my CPU governor was set back to normal.

@fin-ger
Copy link
Member

fin-ger commented Mar 31, 2020

This is being worked on in #107

@fin-ger fin-ger self-assigned this Mar 31, 2020
@fin-ger fin-ger closed this as completed in 10383d7 Apr 5, 2020
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

8 participants