missing frequency value on one of core duo's processors [edgy]

Bug #69139 reported by Andrea Caminiti
4
Affects Status Importance Assigned to Milestone
gnome-cpufreq-applet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

sometimes after booting up my laptop, one frequency value of the frequency monitor applets of my core duo's processors is missing. i can't remember if it's cpu0 or cpu1. to fix it, i have to change the value from frequency to percentage. and then again from percentage to frequency. i will add image of it on the next message. i'm using gnome in spanish. i can't confirm if this happends on other gnome translations.

Andrea Caminiti

Revision history for this message
Andrea Caminiti (nrayever) wrote :

here's the image of the error/bug.

translation:

despues de que arranca mi laptop, uno de los applets de frecuencia de los procesadores de mi core duo, le hace falta el valor en frecuencia. ya no recuerdo si es el cpu0 o cpu1. esto pasa en mi gnome en español. no puedo confirmar si esto pasa en otros idiomas de gnome.

andrea caminiti

Revision history for this message
Chris Lasher (chris.lasher) wrote :

I too am experiencing this bug. No text displays for the applet of either CPU0 or CPU1 unless I go into preferences and select "Show CPU frequency as percentage". At that point, I can switch it back.

Also, when loading as only graphic mode, CPU0 appears a few pixels lower on the taskbar than CPU1. This is alleviated by switching to "Text" in "Appearance" and the switching back.

Is there some output that could help point out where this bug is coming from? I'll be happy to post it.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in gnome-cpufreq-applet:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-cpufreq-applet:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.