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 571824 - cpufreq-applet invisble on panel if no cpufreq module loaded
cpufreq-applet invisble on panel if no cpufreq module loaded
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.25.x
Other Linux
: Normal major
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-15 12:49 UTC by freggy1
Modified: 2013-02-11 22:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description freggy1 2009-02-15 12:49:39 UTC
I'm not sure if I should have reopened http://bugzilla.gnome.org/show_bug.cgi?id=556099 or open this new bug report.

Anyway, the problem seems the same: with GNOME 2.25.90, cpufreq-applet is invisible on the panel. I can right click on the location and then I get the cpufreq-applet menu where I can access its Preferences dialog, but the applet itself, nor the left click menu are visible.

I can make it visible again by changing the appearance in the Preferences dialog. No matter which appearance I chose, it seems the fact that the applet is refreshed, is enough to make it visible again.

gnome-panel-2.25.90-1mdv2009.1
metacity-2.25.144-1mdv2009.1
gnome-applets-2.25.90-1mdv2009.1

Mandriva 2009.1 Cooker x86_64. I'm using the Metacity window manager, but I have compositing in Metacity's gconf settings enabled.
Comment 1 freggy1 2009-02-16 19:03:47 UTC
AFter all, it seems this bug is different from bug #556099: this time, the problem happens when no cpufreq module is loaded when the cpufreq applet loads. As soon as I load a cpufreq module and set the ondemand governor, the applet becomes visible automatically.
Comment 2 nodiscc 2013-02-11 22:22:56 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.