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 471985 - Display more than one CPU at a time
Display more than one CPU at a time
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.18.x
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-30 20:23 UTC by Sven Arvidsson
Modified: 2013-02-11 22:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sven Arvidsson 2007-08-30 20:23:22 UTC 
[ From http://bugs.debian.org/439828 by Marcus Lundblad ]

"It would be nice if the CPU frequency applet would have an option to display more than one CPU (on a multicore CPU). As it is now I have two instances on the applet, one set to display CPU0 and one to CPU1.

When set to only display graphics it would look nice if there where multiple bars
showing the frequence besides the "chip icon". Perhaps such an option should only be available in the "graphics only view", because it would perhaps look cluttered to display numerical values for more than one CPU in the same instance."
Comment 1 avl555 2010-06-21 21:03:59 UTC 
This is also reported here: 590098 (https://bugzilla.gnome.org/show_bug.cgi?id=590098)

And +1 for me!
Comment 2 nodiscc 2013-02-11 22:23:46 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes 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 newer version of GNOME.