GNOME Bugzilla – Bug 338557
cpufreq-applet does not set the governor for cpu being monitored
Last modified: 2010-01-24 01:06:37 UTC
Please describe the problem: cpufreq has a preference to select the monitored cpu. Clicking over the applet, a list of governors is displayed ir order to select one of them. However, the applet internally calls cpufreq-selector without specifying the monitored cpu. Then, the governor is always applied to the default cpu (0 in the current implementation). This bug can be noticed in multicore cpus. Steps to reproduce: 1. Grab a machine with multicore enabled. 2. Add the applet. 3. Select a cpu different to zero. 4. Change the governor. Actual results: The governor is set to the cpu zero, not the monitored. Expected results: The monitored cpuś governor should be changed. Does this happen every time? Yes. Other information: A patch, but this simple bug guide is too stupid and let me change to the classic bugzilla way.
Created attachment 63538 [details] [review] Patch to set the governor of any monitored cpu. Patch to set the speed of any monitored cpu.
This bug is similar to http://bugzilla.gnome.org/show_bug.cgi?id=337578
Hi tigrux, thanks a lot for the patch. I'm going to rewrite the popup-selector soon, so I will fix this bug.
Committed to gnome-2-14.
It should be fixed in head too.
*** Bug 356309 has been marked as a duplicate of this bug. ***