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 380314 - CPU freq menus overcomplicated
CPU freq menus overcomplicated
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: cpufreq
2.16.x
Other All
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-28 22:29 UTC by Brian Kerrick Nickel
Modified: 2006-12-16 16:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Brian Kerrick Nickel 2006-11-28 22:29:26 UTC
The current layout of the menus makes very little sense.
Currently:

Frequencies ->
   o ... GHz
   o ... GHz
   o ... GHz
   -------
   o Automatic (Always Disabled)
Governors -> (Not in alphabetical order)
   o GovB
   o GovA
   o GovC
   o Userspace

Selecting a frequency selects Userspace and sets the frequency.
Selecting Userspace sets the governor and set the frequency to (lowest?)
Selecting a governor changes the governor and marks frequency as automatic.

There is no reason to have two menus, especially when each menu will have only about 5 items in it. Instead, these should be combined into a single menu:

o ... GHz
o ... GHz
o ... GHz
-------
o GovA
o GovB
o GovC

The Governors should be alphabetized and Userspace should be excluded from the list. If Userspace is unavailable, Frequencies should simply not be displayed to avoid user confusion. (As a user I was confused as to why I couldn't change the values.) If no governors are available, the menu should contain a single item. "Learn how to scale frequencies." which goes to a website or yelp.

Other information:
Comment 1 Carlos Garcia Campos 2006-12-06 10:49:49 UTC
Hi Brian, thanks a lot for the report, it sounds quite reasonable. 
Comment 2 Carlos Garcia Campos 2006-12-16 16:15:36 UTC
I've just fixed it in cvs head. Thanks a lot Brian for this so useful bug report.