https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #42 from Ville Aakko <ville.aa...@gmail.com> --- I suspect from the comments (someone involved in the project correct me if I'm wrong) that System Monitor will not be fixed. It's codebase seems too hairy, no-one seems to actually know what the real issue is properly. Note: as I've said before, the **bulk** of the problem is not gathering process information, although I'm fairly certain that problem also has problems. The CPU usage is abnormally high when just drawing sensors information from lm-sensors. Generally, bug listings should be reserved for comments only relevant working towards fixing the issue. However if this seems unlikely, comments about alternatives should be allowed (IMHO); so the comments marked as spam should not be marked as such. I don't see much ranting here. I've already moved on to alternatives. Projects such as btop (for terminal) coolercontrol work well for showing sensor information. I'd be interested in any efforts/projects to start from scratch building a working monitoring application for KDE Plasma. I don't know if I'd be able to contribute, but I've used a lot of different monitoring applications (geared for servers and desktops alike) and know of a few caveats, in addition to resource usage. For example, there's a long-standing (from ksysguard) issue of assuming static structures in /sys/class/hwmon (see bug #466277), which get's exacerbated every year since more and more devices get lm-sensors support (my computer has 7-9 hwmon devices, depending on which USB devices I have plugged in). For a to-be application, a list of minimum set of requirements should be made before starting any development work (judging from the state of Plasma System Monitor, this was not the case when it was developed). -- You are receiving this mail because: You are watching all bug changes.
