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 599881 - Appled does not update from "scaling_available_frequencies" after selecting another CPU with different frequencies
Appled does not update from "scaling_available_frequencies" after selecting a...
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-28 09:05 UTC by cmichael
Modified: 2020-11-06 19:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description cmichael 2009-10-28 09:05:27 UTC
If you start the appled / add it to the panel it starts with CPU0 (default) and reads the list of available frequencies from 

/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies


If you change the CPU to monitor then it seems not to read the available frequencies again.
If you select a frequency from the applets list where you know the different frequency should be instead or if you manually select it by writing it to "scaling_setspeed" the appled is displaying it correctly in the panel but still shows the wrong / old list in the drop-down menu.


This *could* affect users with multi-cpu systems ( untested bacsue I have none ) and users that are able to alter the frequencies on a multi-core system ( tested ).

Looks like that (can not make screenshot when drop down menu is showed)

[  (O[] 1,87GHz  ] <-- real current selected speed
-----------------------------------------------------
-----------------
| o 2.41 GHz     |
| o 2.40 GHz     |
| x 1.60 GHz     | <--- wrong entry
| o 800 MHz      |
|----------------|
| o conservative |
| o ondemand     |
| o performance  |
| o powersave    |
------------------
Comment 1 cmichael 2009-10-28 09:09:07 UTC
Forgot to say that the CPU to monitor I changed to has different frequencies:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 
2410000 2400000 1600000 800000

cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies 
2410000 2400000 1870000 800000
Comment 2 Fabio Durán Verdugo 2009-11-15 01:58:03 UTC
*** Bug 598851 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2020-11-06 19:57:26 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.