Bug 450829 - Level of precision for CPU usage not useful
Summary: Level of precision for CPU usage not useful
Status: RESOLVED FIXED
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-25 13:06 UTC by Tobias Fella
Modified: 2022-02-25 13:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot (102.81 KB, image/png)
2022-02-25 13:06 UTC, Tobias Fella 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Fella 2022-02-25 13:06:37 UTC 
Created attachment 147115 [details]
Screenshot

SUMMARY

The CPU usage levels have an accuracy (>10 digits) that is not useful and causes the cpu core labels to jump around a lot


STEPS TO REPRODUCE
1. Open Systemmonitor
2. Show History Page (though it can also be seen in overview)
3. Profit

OBSERVED RESULT
Very precise

EXPECTED RESULT
less precise

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Arjen Hiemstra 2022-02-25 13:44:02 UTC 
Can you verify that you're running the same version of ksystemstats as your libksysguard? This problem usually occurs when there's a mismatch between versions and the unit information gets lost somehow. Note that ksystemstats is DBus-activated so you might end up running with an incorrect ksystemstats if your development environment isn't setup to handle that.
Comment 2 Tobias Fella 2022-02-25 13:50:40 UTC 
That does seem to be the problem. Using a distro version of both, it works correctly.

Thanks!