The cpufreq-selector tool of the cpufreq-applet fails to set the frequency/govenor on any cpu other than cpu0. This results in a strange situation where by if an applet monitors a cpu >=1 and an attempt is made to alter the frequency or govenor, then the requested change is made to the frequency/govenor setting of cpu 0 regardless. This bug had been reported up stream, but a patch and corresponding a new ebuild are suggested here.
Created attachment 88764 [details, diff] Fixes the bug The patch as submitted up stream: http://bugzilla.gnome.org/show_bug.cgi?id=344393
Created attachment 88765 [details] A revised ebuild applying the patch Ebuild which applys the patch
Created attachment 88767 [details, diff] Patch to cause the applet to pass the cpu numer to to cpu-selector as is done for frequency control I had missed the fact that the second patch mentioned in the original gnome-applets bug report: http://bugzilla.gnome.org/show_bug.cgi?id=338557 is not included in the 2.14.1 release either.
Bug has been fixed in 2.16, closing. If it's still an issue, don't hesitate to reopen :) Thanks