Bug 376864

Summary:	Motherboard and CPU sensors not seen after upgrade
Product:	[Unmaintained] ksysguard	Reporter:	K.J. Petrie <kde.bugs>
Component:	ksysguardd	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.8.6
Target Milestone:	---
Platform:	PCLinuxOS
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description K.J. Petrie 2017-02-23 23:09:04 UTC

In ksysguard 5.8.5 numerous CPU and Motherboard sensors are visible to the thermal monitoring widget. In version 5.8.6 they are not. Only the GPU and HDD/SSD temperatures are visible.

Function can be restored by logging out, copying the previous version of /usr/bin/ksysguardd over the newer file and logging back in.

Hardware:
AMD FX 8350 CPU
GA-970A-DS3P (Rev 2.0) MB
Asus EN210 (Nvidia) GPU
Maxtor STM325031 HDD
3 SSDs

Comment 1 Christoph Feck 2017-02-23 23:22:31 UTC

The only change in ksysguardd in 5.8.6 is the crash fix for bug 376537, which affects parsing of the output of /proc/stat

Please add a comment with Linux version (uname -r), and output of /proc/stat

Comment 2 K.J. Petrie 2017-02-23 23:47:18 UTC

$ uname -r
4.9.8-pclos1

$ cat /proc/stat   
cpu  73342 75 54660 5070675 9923 4268 3875 0 0 0
cpu0 11129 1 7364 632527 418 327 280 0 0 0
cpu1 11769 32 6561 626557 6201 644 220 0 0 0
cpu2 6724 5 5912 638511 727 397 103 0 0 0
cpu3 8424 6 6533 635593 737 475 189 0 0 0
cpu4 10562 12 7898 632043 568 653 97 0 0 0
cpu5 9823 4 7259 633409 527 633 164 0 0 0
cpu6 6834 11 6155 638454 364 403 84 0 0 0
cpu7 8074 1 6974 633578 380 734 2735 0 0 0
intr 8019356 64 6675 0 0 0 0 0 0 415209 0 0 0 0 0 0 0 1301 2 86772 38048 0 0 0 0 0 0 0 19216 129 0 112770 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 12680671
btime 1487887051
processes 36475
procs_running 1
procs_blocked 0
softirq 3234466 11 1429155 1092 20692 38525 0 145694 606603 0 992694

Comment 3 Justin Zobel 2022-10-31 04:31:56 UTC

Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 K.J. Petrie 2022-10-31 11:10:15 UTC

Indeed, it is five years, I no longer use the same motherboard and on the current MB ksysguard 5.26.1 sees a sensible number of sensors.
I therefore can't give a definitive answer, so I'm closing with Works for me as I'm no longer experiencing the problem and no one else has reported it.