-
Notifications
You must be signed in to change notification settings - Fork 70
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
Comments
According to #48, you only have to remove one file. It would be helpful to put that in the README though. |
I'll put it in the readme. |
What about to undo the changes? |
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? |
I assume it would be reset after restart, not sure though? |
Can anyone confirm how do, and what happens if, I uninstall? |
pstate is resetted after every boot to full frequency range and enabled turbo boost. |
@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. |
This is being worked on in #107 |
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.
The text was updated successfully, but these errors were encountered: