| Summary: | Level of precision for CPU usage not useful | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Tobias Fella <fella> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ahiemstra, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
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. That does seem to be the problem. Using a distro version of both, it works correctly. Thanks! |
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