Ubuntu
kdebase package

ksysguard fails to report cpu_freq in dapper

Bug #6724 reported by hunger
6
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Kubuntu Bugs

Bug Description

Hi there!

ksysguard(d) fails to report the cpu frequency when running on a new dapper linux kernel. It reports the max frequency at all times, even when i.e. the gnome cpu frequency applet reports slower values.

Regards,
Tobias

hunger (hunger)
Changed in kdebase:
assignee: nobody → kubuntu-team
Revision history for this message
Kenny Duffus (kduffus) wrote :

do you still have this problem with latest updates?

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
hunger (hunger) wrote :

Yes I do.

The problem is that ksysguard relies on /proc/cpuinfo to have the current cpu frequency. In kernel 2.6.x that proc-file was changed to always give the bootup cpu frequency.

This bug can not get fixed without major surgery to ksysguard: That must be adapted to use the proper files in /sys as a source of information (or hald) instead of relying on deprecated/obsoleted information in /proc.

hunger (hunger)
Changed in kdebase:
status: Needs Info → Confirmed
Revision history for this message
Anthony Mercatante (tonio) wrote :

Resolved on edgy

Changed in kdebase:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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