| Summary: | KDE System Monitor seems very confused about sensors of Raspberry Pi 5 | ||
|---|---|---|---|
| Product: | [Applications] plasma-systemmonitor | Reporter: | Ellie <el> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | ahiemstra, kde.bugs, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.2 | ||
| Target Milestone: | --- | ||
| Platform: | postmarketOS | ||
| OS: | Linux | ||
| See Also: | https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/3750 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot showing the missing sensor data and an error message showing up when opening system monitor | ||
Make sure that ksystemstats is installed and can be launched using D-Bus autolaunch. From the looks of it, it's not running thus you'll not get any sensors. Currently, it does seem to be running: $ ps aux | grep stats 13076 user 0:15 /usr/bin/ksystemstats 13083 user 0:00 grep stats $ Ok, next step would be running `kstatsviewer --list` to get a list of the sensors known to ksystemstats. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. I've had to format and reinstall the system for various reasons, and the problem still occurs on a Raspberry Pi 5. This suggests to me it's not a customization issue since this is a fresh install with wiped config. I tried to prompt kstatviewer but it seems like Alpine and postmarketOS don't ship it at all. There seems to be no way to install and launch it. This time around however, ksystemstats doesn't seem to be running after booting and unlocking a session. What is the usual way this is meant to be automatically launched? I've had some issues with the home being briefly readonly with this install https://discuss.kde.org/t/i-broke-my-kwallet-auto-login/40205 and it seems like this can cause some initial setup steps of a KDE session not to happen. Normally, D-Bus should autolaunch ksystemstats when something requests stats from it. Unfortunately there isn't an easy way to verify that that's working, other than launching `kstatsviewer --list` or something similar and seeing if that starts ksystemstats. *** Bug 484384 has been marked as a duplicate of this bug. *** Running kstatsviewer --list will start ksystemstats, but then it just reports no sensors available: $ ps aux | grep ksystem 24585 user 0:00 grep ksystem $ kstatsviewer --list No sensors available. $ ps aux | grep ksystem 24589 user 0:30 /usr/bin/ksystemstats 24599 user 0:00 grep ksystem $ kstatsviewer --list No sensors available. $ (I think I previously mistyped the command as kstatviewer instead of kstatsviewer, hence why I erroneously believed it to be missing.) Here's the output of "sensors", which shows that the kernel seems to have some sensors available that are operational:
# sensors
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A
pwmfan-isa-0000
Adapter: ISA adapter
fan1: 2447 RPM
cpu_thermal-virtual-0
Adapter: Virtual device
temp1: +56.8°C
rp1_adc-isa-0000
Adapter: ISA adapter
in1: 2.02 V
in2: 2.57 V
in3: 1.43 V
in4: 1.44 V
temp1: +47.3°C
nvme-pci-10100
Adapter: PCI adapter
Composite: +29.9°C (low = -5.2°C, high = +82.8°C)
(crit = +84.8°C)
Sensor 1: +29.9°C (low = -273.1°C, high = +65261.8°C)
#
|
Created attachment 183126 [details] Screenshot showing the missing sensor data and an error message showing up when opening system monitor SUMMARY KDE System Monitor seems very confused about sensors of Raspberry Pi 5, and doesn't show any useful information other than the process table. This is an OpenRC system, however on my x64 OpenRC install of postmarketOS+Alpine with KDE, the system monitor works. Therefore, something about this seems to be specific to a Raspberry Pi 5. I already poked the distribution about this, but they seem to be clueless as well. My apologies if this turns out to be a distribution and packaging issue after all. STEPS TO REPRODUCE 1. Open KDE system monitor with a KDE install on Raspberry Pi 5 using Alpine or postmarketOS (I haven't tested Raspberry Pi OS) OBSERVED RESULT No sensor data is shown, not even free memory. EXPECTED RESULT The sensor data works. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: postmarketOS Edge based on Alpine Edge (ARM64, bug might be limited to this architecture) KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.15.0 Qt Version: 6.8.3 ADDITIONAL INFORMATION