When coming back on from suspend the frequency number doesn't change no matter what profile I use.

I am the maintainer of this extension for Arch Linux, been debugging why it doesn't work in 3.26 and hoping this issue can help track that:

Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 67]: reference to undefined property "out"
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 67]: Too many arguments to function GLib.spawn_command_line_sync: expected 1, got 2
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 71]: Too many arguments to function GLib.spawn_command_line_sync: expected 1, got 2
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 75]: Too many arguments to function GLib.spawn_command_line_sync: expected 1, got 2
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 153]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 157]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
Oct 14 06:15:23 holodeck.local gnome-shell[8065]: JS WARNING: [/usr/share/gnome-shell/extensions/[email protected]/src/indicator.js 189]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2

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.

Add Localization

On Fedora 26, how can I uninstall whatever helper I installed from within the extension?

Thank you in advance.

Please, extend the notification by adding a submenu with 2 options:
1 - to present pidgin conversation window
2 - to show window list.

@MarPiRK
@honza-kasik
May I bother you to add some translations I recently introduced?
For german and english I added them myself.

Some cool additional features for profiles would be:

• switch devices on/off (bluetooth, hdd spin down time, etc.)
• set display brightness

The user should be able to save space on the taskbar by hiding the icon of the extension.

For no reason the widget does not appear anymore after turning on with the shell extensions website.

• pstate is enabled

$ ls /sys/devices/system/cpu/cpu0/cpufreq/
affected_cpus
related_cpus
scaling_max_freq
cpuinfo_cur_freq
scaling_available_governors
scaling_min_freq
cpuinfo_max_freq
scaling_cur_freq
scaling_setspeed
cpuinfo_min_freq
scaling_driver
cpuinfo_transition_latency
scaling_governor

• Intel Core i5-4200U CPU Haswell mobile
• Ubuntu 16.04.3 LTS
• Kernel: 4.4.0-104-generic
• policykit 0.105-2ubuntu2
• GNOME Shell 3.18.5

$ journalctl -xb | grep [email protected]
Dez 18 04:31:17 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: sed -i "s/xxxPATHxxx//home/tommy/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl/" /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy
Dez 18 04:31:17 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: Kindprozess »/home/tommy/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl« konnte nicht ausgeführt werden (Keine Berechtigung)
Dez 18 04:32:14 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: Extension "[email protected]" had error: TypeError: _indicator is undefined
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/sr@latin/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/cs_CZ.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/installer.sh
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/en_US.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/unsupported.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/ru/LC_MESSAGES/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/data/icons/cpu.svg
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/de_DE.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/de/LC_MESSAGES/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/convenience.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/sr@latin/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/fr_FR.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/en/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/pl/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/sr/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/profilebutton.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/ru_RU.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/notinstalled.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/pl_PL.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/fr/LC_MESSAGES/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/preferences.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/sr_RS.po
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/data/mko.cpupower.policy.in
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/de/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/sr/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/baseindicator.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/indicator.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/data/cpupower-preferences.glade
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/cs/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/schemas/org.gnome.shell.extensions.cpupower.gschema.xml
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/ru/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/profile.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/LICENSE
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/pl/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/cpufreqctl
Dez 18 04:32:20 tommy-dell gnome-session[2103]: creating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/en/LC_MESSAGES/
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/schemas/gschemas.compiled
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/utils.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/[email protected]
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/template.pot
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/extension.js
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/en/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: inflating: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/locale/fr/LC_MESSAGES/gnome-shell-extension-cpupower.mo
Dez 18 04:32:20 tommy-dell gnome-session[2103]: extracting: /home/tommy/.local/share/gnome-shell/extensions/[email protected]/metadata.json
Dez 18 04:32:20 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: Kindprozess »/home/tommy/.local/share/gnome-shell/extensions/[email protected]/src/installer.sh« konnte nicht ausgeführt werden (Keine Berechtigung)
Dez 18 04:35:54 tommy-dell sudo[4174]: tommy : TTY=pts/1 ; PWD=/home/tommy ; USER=root ; COMMAND=/bin/cp /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy /usr/share/polkit-1/actions/
Dez 18 04:42:43 tommy-dell sudo[5170]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/cp /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy /usr/share/polkit-1/actions/
Dez 18 04:43:23 tommy-dell sudo[5267]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/cp /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy /usr/share/polkit-1/actions/
Dez 18 04:44:14 tommy-dell sudo[5394]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/cp /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy /usr/share/polkit-1/actions/
Dez 18 04:46:11 tommy-dell sudo[5668]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/cp /home/tommy/.local/share/gnome-shell/extensions/[email protected]/mko.cpupower.policy /usr/share/polkit-1/actions/
Dez 18 04:46:49 tommy-dell sudo[5802]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/chown root:root /home/tommy/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl
Dez 18 04:46:51 tommy-dell sudo[5810]: tommy : TTY=pts/1 ; PWD=/usr/share/polkit-1/actions ; USER=root ; COMMAND=/bin/chmod 0555 /home/tommy/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl
Dez 18 04:47:08 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: Kindprozess »/home/tommy/.local/share/gnome-shell/extensions/[email protected]/installer.sh« konnte nicht ausgeführt werden (Keine Berechtigung)
Dez 18 04:47:43 tommy-dell gnome-session[2103]: Gjs-Message: JS LOG: Kindprozess »/home/tommy/.local/share/gnome-shell/extensions/[email protected]/installer.sh« konnte nicht ausgeführt werden (Keine Berechtigung)
Dez 18 04:51:06 tommy-dell gnome-session[2103]: Gjs-Message: JS WARNING: [/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js 436]: anonymous function does not always return a value
Dez 18 04:51:06 tommy-dell gnome-session[2103]: Gjs-Message: JS WARNING: [/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js 465]: anonymous function does not always return a value
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.selectionChanged@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:498
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.initConfigWidget/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:341
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshUI@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:519
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.loadConfig/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:538
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.profiles@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:592
Dez 18 04:51:22 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshProf@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:543
Dez 18 04:51:22 tommy-dell gnome-session[2103]: EditDialog<.run/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:130
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.selectionChanged@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:498
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.initConfigWidget/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:341
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshUI@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:519
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.loadConfig/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:538
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.profiles@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:592
Dez 18 04:51:28 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshProf@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:543
Dez 18 04:51:28 tommy-dell gnome-session[2103]: EditDialog<.run/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:130
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.selectionChanged@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:498
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.initConfigWidget/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:341
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshUI@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:519
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.loadConfig/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:538
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.profiles@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:592
Dez 18 04:51:49 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshProf@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:543
Dez 18 04:51:49 tommy-dell gnome-session[2103]: EditDialog<.run/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:130
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.selectionChanged@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:498
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.initConfigWidget/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:341
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshUI@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:519
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.loadConfig/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:538
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.profiles@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:592
Dez 18 04:51:58 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshProf@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:543
Dez 18 04:51:58 tommy-dell gnome-session[2103]: EditDialog<.run/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:130
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.selectionChanged@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:498
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.initConfigWidget/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:341
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.refreshUI@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:519
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.loadConfig/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:538
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.show_freq_taskbar@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:599
Dez 18 04:52:11 tommy-dell gnome-session[2103]: CPUPowerPrefsWidget<.addSwitch/<@/home/tommy/.local/share/gnome-shell/extensions/[email protected]/prefs.js:293

Creating a new issue

• Check if another issue with the same problem exists
• Check if you got the prerequisites right
  • pstate driver enabled and supported CPU
  • policykit working and rule working
• Check if the cpufreqctl utility works correctly
• Please include the following information (only for bugreports):
  • CPU Model
  • Linux kernel version
  • policykit version
  • Gnome shell version
  • journalctl -xb (maybe pastebin/filtered)

it would be nice to be able to hide the arrow beside the actual icon to reduce the extension's footprint.

I think this extension should be able to save last applied settings and apply them on resume after suspend or restart/startup. Some settings are overridden by cpupower.service or by tlp.service (if used) on startup. I've been able to disable cpupower and mask it, to let tlp apply my settings. I've set in tlp the procentages I want by default and the governor for AC or BAT. I think the governor would be a new nice feature to add to this extensions.

Subject

Everything works correctly, but I accidentally added an entry without a blank name. This resulted in an error in which metadata information about the package is displayed instead of the name of the mode. Please see the attached screenshot.

Can you add an option to place the extention in top right menu please?

Whereas /proc/cpuinfo says :

cat /proc/cpuinfo |grep "cpu MHz"
cpu MHz     : 1422.851
cpu MHz     : 2302.539
cpu MHz     : 2299.609
cpu MHz     : 1470.410

Thank you for this great extension!

I just wanted to share, that throttling suddenly stopped to work on my device around a month ago, obviously since Fedora 26/27 updated their kernel packages to 4.13.x.

Since I downgraded to 4.12.12 kernel packages the extension behaves fine again.

I found this Reddit post and some kernel Git notes:

Linux 4.13 doesn't show the current frequency in /proc/cpuinfo anymore [...]

So maybe similar code as https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/pull/404/files would do?

Hi, on my ivybridge laptop, whatever setting I change (min freq, max freq, turbo ecc) the cpu frequency won't go beyond 800MHz even in high load (my CPU max freq is 2.5GHz).

This line in the extension settings (pref.js)

const GWeather = imports.gi.GWeather;

causes the prefs gui to not load if gir1.2-gweather is not installed, which was not on my system. I don't see any reason to require this dependency.

I have correctly installed the extension and it is working so far however if I run some up that use a lot of cpu the max limit is automatically changed.

I'm not sure if this happens because of some kind of HW controller on the frequency. ( I'm not running thermald or other similar software )

OS: Antergos (Arch linux)
CPU: Sandybridge ( Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz)

Correct if I'm wrong, but you polkit action authorizes running a script owned by the normal user without any authorization. A malicious agent which gains access to the computer (but does not know the root password) can edit that script, effectively being able to run any command. Perhaps I'm missing something ? Shouldn't you make the script only writable by root ?

It would be very nice to have checkbox for this option.

The extension should update not only the current frequency, but also the min/max speed values and the turbo boost.

(reported by lamiska)

It displays the frequency, but it won't change the frequency. When it tries to change the frequency, I have to enter the password four times (once for each core), but then nothing changes. Running any one of the following in terminal does, however, work on all cores:

sudo cpupower frequency-set -g powersave
sudo cpupower frequency-set -g conservative
sudo cpupower frequency-set -g ondemand
sudo cpupower frequency-set -g performance

All installation instructions were followed to the letter and the newest from GIT is installed. The names of governors in the list in preferences also do not match the names of those actually installed.

Running pkexec ~/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl max 100 gives the following error:

/home/XXXXXX/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl: line 47: /sys/devices/system/cpu/intel_pstate/max_perf_pct: No such file or directory

This is on a system running Fedora 23 Workstation, GNOME Shell 3.18.4. Processor is Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz

It hangs immediately after it, the TTY{X} works though. Moving the cursor works as well, nothing else does. GDM works too. Restarting doesn't help so I removed the extension from FS.

Hello,

Tried to install it from extension.gnome.org as well as extracting the zip from github to extensions folder and running the policy installation script. I get the following error for preferences in tweakui and extension does not start.

Gtk.BuilderError: /home/swaroop/.local/share/gnome-shell/extensions/[email protected]/data/cpupower-preferences.glade:75:1 requires attribute "id"

Stack trace:
CPUPowerPreferences<._init@/home/swaroop/.local/share/gnome-shell/extensions/[email protected]/src/preferences.js:56
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
_Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110
Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:204
buildPrefsWidget@/home/swaroop/.local/share/gnome-shell/extensions/[email protected]/prefs.js:41
Application<._selectExtension@/usr/share/gnome-shell/js/extensionPrefs/main.js:102
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Application<._extensionSelected@/usr/share/gnome-shell/js/extensionPrefs/main.js:121
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Application<._selectExtension@/usr/share/gnome-shell/js/extensionPrefs/main.js:112
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Application<._extensionsLoaded@/usr/share/gnome-shell/js/extensionPrefs/main.js:221
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
_emit@resource:///org/gnome/gjs/modules/signals.js:124
ExtensionFinder<._extensionsLoaded@/usr/share/gnome-shell/js/misc/extensionUtils.js:178
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
done@/usr/share/gnome-shell/js/misc/fileUtils.js:33
_collectFromDirectoryAsync/</<@/usr/share/gnome-shell/js/misc/fileUtils.js:51
onNextFileComplete@/usr/share/gnome-shell/js/misc/fileUtils.js:21
main@/usr/share/gnome-shell/js/extensionPrefs/main.js:278
@:1

Ran the following diagnostics:
cmd: "gnome-shell --version"
result: "GNOME Shell 3.10.4"

cmd: "grep -i pstate /boot/config-$(uname -r)"
result: "CONFIG_X86_INTEL_PSTATE=y"

cmd: "sudo ./installer.sh install"
result : "Installing policykit action... Success
Fixing permissions... Success"

cmd: "sudo ./installer.sh check"
result: "Installed"

cmd: "./cpufreqctl min get" (similar for turbo and max)
result: "./cpufreqctl: line 206: /sys/devices/system/cpu/intel_pstate/min_perf_pct: No such file or directory"

CPU model: "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"

Linux kernel: "Linux MAVLAB5 3.13.0-141-generic #190-Ubuntu SMP Fri Jan 19 12:52:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux"

policykit version: 0.105-4ubuntu3.14.04.1

Do you have any plans to enable the governor to be set?

Should be able to:

• Set which frequency is displayed
• Manage profiles
• Setup startup/hibernation/dbus integration

Gnome Shell 3.16
Processor: Intel® Core™ i5-4200U CPU @ 1.60GHz × 4
Graphics: Intel® Haswell Mobile
intel_pstate enabled in kernel

and by not working, I meant that the current frequency is stuck at 0mhz

Profile classes

This extension was working fine on my Arch Linux with GNOME 3.22 but today's extension update from the GNOME Extensions website results in a complete hang of the entire system and I have to manually rm the extension folder from a tty to have a working system again. Going back to the previous version of this extension resolves the issue for me.

Could you please fix this?

(btw, someone on 3.20 also reported this issue on the GNOME Extensions website so I'm not the only one)

I'm losing the bullet point next to the profile. I'm noticing that the bullet point when selecting a profile is missing after reopening the extension from the top bar. So it's a little tough to remember which profile I'm on after awhile. I'm on Gnome 3.18 Gentoo kernel 4.5.2.

If you get the same value as above, everything is working and you can proceed to the next step.

What's the next step? I did all steps, installed the extension and couldn't see any new icon in my toolbar. My model seems compatible:

$ ls /sys/devices/system/cpu/intel_pstate/
max_perf_pct  min_perf_pct  no_turbo

.local/bin/cpufreqctl: line 54: /sys/devices/system/cpu/intel_pstate/min_perf_pct: No such file or directory

/sys/devices/system/cpu/
/sys/devices/system/cpu/cpu0
/sys/devices/system/cpu/cpu0/cache
/sys/devices/system/cpu/cpu0/cache/power/control
/sys/devices/system/cpu/cpu0/cache/power/async
/sys/devices/system/cpu/cpu0/cache/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/cache/power/runtime_active_time
/sys/devices/system/cpu/cpu0/cache/index0/power/control
/sys/devices/system/cpu/cpu0/cache/index0/power/async
/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/cache/index0/power/runtime_active_time
/sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_map
/sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_list
/sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size
/sys/devices/system/cpu/cpu0/cache/index0/physical_line_partition
/sys/devices/system/cpu/cpu0/cache/index0/ways_of_associativity
/sys/devices/system/cpu/cpu0/cache/index1/power/control
/sys/devices/system/cpu/cpu0/cache/index1/power/async
/sys/devices/system/cpu/cpu0/cache/index1/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/cache/index1/power/runtime_active_time
/sys/devices/system/cpu/cpu0/cache/index1/shared_cpu_map
/sys/devices/system/cpu/cpu0/cache/index1/shared_cpu_list
/sys/devices/system/cpu/cpu0/cache/index1/coherency_line_size
/sys/devices/system/cpu/cpu0/cache/index1/physical_line_partition
/sys/devices/system/cpu/cpu0/cache/index1/ways_of_associativity
/sys/devices/system/cpu/cpu0/cache/index2/power/control
/sys/devices/system/cpu/cpu0/cache/index2/power/async
/sys/devices/system/cpu/cpu0/cache/index2/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/cache/index2/power/runtime_active_time
/sys/devices/system/cpu/cpu0/cache/index2/shared_cpu_map
/sys/devices/system/cpu/cpu0/cache/index2/shared_cpu_list
/sys/devices/system/cpu/cpu0/cache/index2/coherency_line_size
/sys/devices/system/cpu/cpu0/cache/index2/physical_line_partition
/sys/devices/system/cpu/cpu0/cache/index2/ways_of_associativity
/sys/devices/system/cpu/cpu0/cache/index3/power/control
/sys/devices/system/cpu/cpu0/cache/index3/power/async
/sys/devices/system/cpu/cpu0/cache/index3/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/cache/index3/power/runtime_active_time
/sys/devices/system/cpu/cpu0/cache/index3/shared_cpu_map
/sys/devices/system/cpu/cpu0/cache/index3/shared_cpu_list
/sys/devices/system/cpu/cpu0/cache/index3/coherency_line_size
/sys/devices/system/cpu/cpu0/cache/index3/physical_line_partition
/sys/devices/system/cpu/cpu0/cache/index3/ways_of_associativity
/sys/devices/system/cpu/cpu0/power/control
/sys/devices/system/cpu/cpu0/power/async
/sys/devices/system/cpu/cpu0/power/runtime_active_kids
/sys/devices/system/cpu/cpu0/power/runtime_active_time
/sys/devices/system/cpu/cpu0/crash_notes
/sys/devices/system/cpu/cpu0/crash_notes_size
/sys/devices/system/cpu/cpu0/topology/core_id
/sys/devices/system/cpu/cpu0/topology/core_siblings
/sys/devices/system/cpu/cpu0/topology/core_siblings_list
/sys/devices/system/cpu/cpu0/topology/physical_package_id
/sys/devices/system/cpu/cpu0/microcode
/sys/devices/system/cpu/cpu0/microcode/processor_flags
/sys/devices/system/cpu/cpu1
/sys/devices/system/cpu/cpu1/cache
/sys/devices/system/cpu/cpu1/cache/power/control
/sys/devices/system/cpu/cpu1/cache/power/async
/sys/devices/system/cpu/cpu1/cache/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/cache/power/runtime_active_time
/sys/devices/system/cpu/cpu1/cache/index0/power/control
/sys/devices/system/cpu/cpu1/cache/index0/power/async
/sys/devices/system/cpu/cpu1/cache/index0/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/cache/index0/power/runtime_active_time
/sys/devices/system/cpu/cpu1/cache/index0/shared_cpu_map
/sys/devices/system/cpu/cpu1/cache/index0/shared_cpu_list
/sys/devices/system/cpu/cpu1/cache/index0/coherency_line_size
/sys/devices/system/cpu/cpu1/cache/index0/physical_line_partition
/sys/devices/system/cpu/cpu1/cache/index0/ways_of_associativity
/sys/devices/system/cpu/cpu1/cache/index1/power/control
/sys/devices/system/cpu/cpu1/cache/index1/power/async
/sys/devices/system/cpu/cpu1/cache/index1/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/cache/index1/power/runtime_active_time
/sys/devices/system/cpu/cpu1/cache/index1/shared_cpu_map
/sys/devices/system/cpu/cpu1/cache/index1/shared_cpu_list
/sys/devices/system/cpu/cpu1/cache/index1/coherency_line_size
/sys/devices/system/cpu/cpu1/cache/index1/physical_line_partition
/sys/devices/system/cpu/cpu1/cache/index1/ways_of_associativity
/sys/devices/system/cpu/cpu1/cache/index2/power/control
/sys/devices/system/cpu/cpu1/cache/index2/power/async
/sys/devices/system/cpu/cpu1/cache/index2/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/cache/index2/power/runtime_active_time
/sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
/sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_list
/sys/devices/system/cpu/cpu1/cache/index2/coherency_line_size
/sys/devices/system/cpu/cpu1/cache/index2/physical_line_partition
/sys/devices/system/cpu/cpu1/cache/index2/ways_of_associativity
/sys/devices/system/cpu/cpu1/cache/index3/power/control
/sys/devices/system/cpu/cpu1/cache/index3/power/async
/sys/devices/system/cpu/cpu1/cache/index3/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/cache/index3/power/runtime_active_time
/sys/devices/system/cpu/cpu1/cache/index3/shared_cpu_map
/sys/devices/system/cpu/cpu1/cache/index3/shared_cpu_list
/sys/devices/system/cpu/cpu1/cache/index3/coherency_line_size
/sys/devices/system/cpu/cpu1/cache/index3/physical_line_partition
/sys/devices/system/cpu/cpu1/cache/index3/ways_of_associativity
/sys/devices/system/cpu/cpu1/power/control
/sys/devices/system/cpu/cpu1/power/async
/sys/devices/system/cpu/cpu1/power/runtime_active_kids
/sys/devices/system/cpu/cpu1/power/runtime_active_time
/sys/devices/system/cpu/cpu1/crash_notes
/sys/devices/system/cpu/cpu1/crash_notes_size
/sys/devices/system/cpu/cpu1/topology/core_id
/sys/devices/system/cpu/cpu1/topology/core_siblings
/sys/devices/system/cpu/cpu1/topology/core_siblings_list
/sys/devices/system/cpu/cpu1/topology/physical_package_id
/sys/devices/system/cpu/cpu1/microcode
/sys/devices/system/cpu/cpu1/microcode/processor_flags
/sys/devices/system/cpu/cpuidle
/sys/devices/system/cpu/cpuidle/current_driver
/sys/devices/system/cpu/cpuidle/current_governor_ro
/sys/devices/system/cpu/power/control
/sys/devices/system/cpu/power/async
/sys/devices/system/cpu/power/runtime_active_kids
/sys/devices/system/cpu/power/runtime_active_time
/sys/devices/system/cpu/microcode

Hi, enjoying your extension for a while.
The only thing I wish it had is to set default profiles in battery and AC modes.

Does anyone knows an easy way to achieve this (preferably without dbus monitoring) ?

Currently I am running below commands in gdm startup. Would like to trigger scripts when adapter connect/disconnect...
thanks....

pkexec ~/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl min 0
pkexec ~/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl max 90
pkexec ~/.local/share/gnome-shell/extensions/[email protected]/cpufreqctl turbo 0

After switching between profiles for the cpu frequencies the frequency number does not change.

The entire shell freezes every 2 seconds for about 100-300 ms.

GNOME Shell 3.26.1
Extension as of 295f38b
CPU: i7 6700K
Kernel: 4.13.0-16-generic

Respond to DBus events such as ac/battery change and change cpu frequency

In my case before suspending , I use high performance profile on AC, then after resuming my system, I use slower cpu setting, set by TLP, but cpupower set it back to high profile. Please add option to not restoring last setting

Thanks

If I set the minimal frequency to 22% or higher all is fine - means the settings keep saved.
When I set to lower then 22% (0-21%) it always switch back to 22% ?! Directly when set (1 sec delay or so).
The same goes for the maximal frequence.. The minimal setting I can use is 22 %...

Any idea why or how to troubleshoot?

I've installed your extension following your instructions. Tweak tools shows the extension is successfully installed, and the extension's configuration menu (from tweak tools) only shows me the chance of showing the current CPU freq. But anyway, I see no icons to change CPU governors.

Some data of my laptop: MSI GE60 422XES. Kernel 3.16.0-43, i5-4210H (governors available are only powersave and performance). gnome-shell version 3.10.4. Ubuntu 14.04.

The gnome-shell looking glass shows me no errors.

Request for enhancement

It would be very nice if one could see which profile is currently selected (maybe a simple check mark on the last selected profile or so)

I turn off "turbo boost",but it will be enbaled after reboot.How can I keep it on?thanks.

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>

When I type gnome-shell -r, I get:

CPU Power Manager-Message: 09:47:17.770: Inside cpupower.CPUFreqIndicator
Gjs-Message: 09:47:17.958: JS WARNING: [/home/piegames/.local/share/gnome-shell/extensions/[email protected]/src/indicator.js 169]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
Gjs-Message: 09:47:17.959: JS WARNING: [/home/piegames/.local/share/gnome-shell/extensions/[email protected]/src/indicator.js 173]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
CPU Power Manager-Message: 09:47:17.961: 21 100
Gjs-Message: 09:56:30.259: JS WARNING: [/home/piegames/.local/share/gnome-shell/extensions/[email protected]/src/indicator.js 205]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2

Hardware information:

• CPU Model: Intel i7 7th Gen
• Linux kernel version 4.17.2-1-ARCH
• Gnome shell version: 3.28.2

The extension seems to be working fine though, it's just an annoying spam in my logs.

There is this nice script that does thermal throttling: https://github.com/Sepero/temp-throttle/

It's just a loop polling the temperature and changing the max frequency until that temperature is below a threshold.

I think it would be a nice addition to have such features and not that hard to implement. (Since it is using another interface than this extension, it might be faster to re-implement it from scratch)

After suspending, the extension does not retain the configuration, and loses the ability to change de CPU configuration. If I choose a profile, the extension apparently switches to that profile, but frequency never changes.

Version information:

Shell version: 3.14.4
Extension version: 4

reported by cplopez

The installation guide advises to copy the policy file from the users extension installation folder to /usr/share/polkit-1/actions/. The file contains a reference to the cpufreqctl binary in the users extension folder. The policy will apply to this binary only.

When a second user on the same system installs the extension and follows the installation procedure, the policy is overwritten by the version of the new user which point to his local version of cpufreqctl.

A the result the first user has to authenticate now on any change. Applying a profile may require multiple authentications.

I fixed the problem locally by copying the binary to /usr/local/bin/, setting cpufreqctl_path accordingly and changing <annotate key="org.freedesktop.policykit.exec.path"> in the policy file.