SUMMARY In my system I have the following network interfaces: lo, wlan0, eth0, docker0, tun0. When adding a new network interface tun1 by starting another VPN service, some of the system monitoring widgets on my desktop suddenly become associated to different sensors. For example, the "Core 0" temperature sensor becomes "tun1 Transmitter FIFO overrun rates". Somehow, the read value seems to be correct, but is reported in wrong units: before starting the VPN I had a read of 34.0C, and after I get 34 s^-1. Stopping the VPN (thus removing tun1) the things get back to normality. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0
Another case that might be useful to track down the bug: - Initial situation: lo, eth0, wlan0 - Action: add tun0 by starting a VPN service - Result: the "CPU 1" sensor of the "Individual Core Usage" widget becomes "Paged out Pages". All the other cpu sensors (from 2 to 12 in my system) are changed as well (e.g. "CPU 2" -> "lo Receiver Errors Rate").
The bug is present also in Plasma 5.19.1
I'd say messing with the configuration of these widgets, in general, breaks them. I just lost the whole "Line Chart Details" page after tweaking things a bit.
Still present in 5.19.2.
For me too in 5.19.2 Memory Sensors and fans as well as ethernet up/down and usage of Drives are not affected in my setup.
Still present in 5.19.3.
Still present in 5.19.4.
Additional way to reproduce this: start a container or VM
@Matthias Homann: I think the underlying cause is the same I described, i.e. starting a container or a VM creates network interfaces.
(In reply to Nicola Mori from comment #9) > @Matthias Homann: I think the underlying cause is the same I described, i.e. > starting a container or a VM creates network interfaces. definitely: run as root: "nmcli con add type bridge ifname testbridge name testbridge" and you'll see the same effect... Deleteing that bridge returns the disk usage monitor to normal, but not the CPU monitor...
looks as if it's only network interfaces that cause this - plugging in an usb drive doesn't mess up the sensors. also: it's not related to NetworkManager, my other openSUSE box uses wickedd instead and has the same issues.
Should be fixed by https://invent.kde.org/plasma/ksysguard/-/merge_requests/30
Thanks David, I built a patched version of ksysguard and I confirm that the patch you linked fixes the problem for me.
I confirm that the bug is fixed in 5.19.5. Thanks!