https://bugs.kde.org/show_bug.cgi?id=434922
--- Comment #2 from Sergio <sergio.calleg...@gmail.com> --- As mentioned, ksystemstats appears to be active and jumps to 100% CPU usage by adding the plasmoids. So it seems to get started appropriately, but then something goes wrong. The issue is immediately present after adding the plasmoid, not just a login. I have noticed that other cpu-load related plasmoids that can be downloaded rather than being readily available appear to work, though partially. However, with them, ksystemstats does not seem to run (e.g., I see that the "system load viewer" plasmoid version 0.8 by Martin Yrjölä works, even if the "show CPUs separately" option does not). Is it based on a different approach? Also running ksysguard works (as mentioned) and does not start ksystemstats. Hence, my impression is that some plasmoid rely on a "new" framework using the ksystemstats daemon, that the daemon gets started properly when needed, but does not work. It fails to provide data to the plasmoids and it enters some state where it uses all the available resources of the core it runs on. I wonder if this is ARM specific or RPI4 specific or is due to a packaging or permission problem specific to arch/manjaro. -- You are receiving this mail because: You are watching all bug changes.
