After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728217 - cpufreq-applet doesn't show percentage freq on gnome startup
cpufreq-applet doesn't show percentage freq on gnome startup
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.10.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-14 21:51 UTC by Stéphane Aulery
Modified: 2014-04-15 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stéphane Aulery 2014-04-14 21:51:18 UTC 
Reported from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315726

On gnome startup, cpufreq-applet shows CPU as frequency, even if
percentage has been set in prefrences.

Preference is remembered but shown value is a frequency.

A way to see it as percentage again is re-set it in preferences (set "CPU as
freq" and back with "CPU as percentage").

At next gnome startup it will be re-shown as freq.

greetings,
Comment 1 André Klapper 2014-04-15 13:13:58 UTC 
You are using version 2.10.x which is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that older version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

Please feel free to reopen this bug if the problem still occurs with a recent version of GNOME, or feel free to file a bug report in the bug tracking system of your Linux distribution if your distribution still supports your version 2.10.x

(I don't see much sense in forwarding eight year old bug reports to upstream without any indicators that this is still a problem in GNOME 3.x or at least 2.32.)