Bug 463761

Summary: CPU utilization will not stack as in previous version, also cannot resize graphs to make them readable. Often they blow past the bottom of the window as they are too small.
Product: [Applications] plasma-systemmonitor Reporter: dmoak <dmoak>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ahiemstra, nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.24.4   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description dmoak 2023-01-03 00:33:23 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. add window to show cpu usage
2. There is no way to show a sum off all CPU usage (e.g. 4 cores at 100% should stack to 400%, as it would in previous versions--not possible now... plus there is no history on combined toilet-bowl indicators... so you miss spikes)
3. Additionally, there is no way to resize or stretch the display area so if you have a CPU graphs, they just run out the bottom.. so... to duplicate, add 8 cpu monitors.
4. The combination of these two bugs makes it impossible to gage overall system CPU loadings as threads are passed from core to core over time.  Please see the sysguard that shipped with Kubuntu 20.04 and earlier for proper behavior of the CPU and other widgets.

OBSERVED RESULT

display corruption and overall illegible/useless displays

EXPECTED RESULT
Stacked CPU utilization for each core

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

ADDITIONAL INFORMATION
I would expect this to be consistent across all versions of this package and across OS's.
Comment 1 Nate Graham 2023-01-09 18:58:01 UTC
> also 
Thanks for the bug report! Unfortunately this bug reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation.

Can you ask you to open a new bug report for each specific issue? Thanks again!
Comment 2 Nate Graham 2023-04-03 20:31:17 UTC

*** This bug has been marked as a duplicate of bug 434040 ***