Comment 2 for bug 6724

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.