Bug 402755

Summary: Wrong display for CPU4 load in System Load tab
Product: [Unmaintained] ksysguard Reporter: virus.d.tected <virus.d.tected>
Component: ksysguardAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: richard.llom
Priority: NOR    
Version First Reported In: 5.13.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: top left window is GNOME-system-monitor, bottom right window is Ksysguard. Notice the load readings, specifically for CPU4

Description virus.d.tected@gmail.com 2019-01-01 13:54:05 UTC
Created attachment 117224 [details]
top left window is GNOME-system-monitor, bottom right window is Ksysguard. Notice the load readings, specifically for CPU4

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION
Comment 1 virus.d.tected@gmail.com 2019-01-01 14:01:44 UTC
Forgot to mention, I installed Ksysguard from Ubuntu Software Centre. Running Ubuntu 18.10 from a persistent live USB drive I created and updated yesterday.

System spec is as follows:

Asrock z170 OC Formula
Intel Core i5 7400
16gb ram @ 2400Mhz

Overall the system is stable, responsive and no other resource/system monitors available on the software centre are reporting 100% load on any devices or cores.
Comment 2 Richard Llom 2019-03-12 19:33:20 UTC
Do you still have this issue?

What happens if you create a new tab and create a new graph for CPU load, does it have the same issue?

When you right click on the graph -> Properties, what does it say under Sensors?
Comment 3 Bug Janitor Service 2019-03-27 04:33:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-04-11 04:33:18 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!