Using Plasma 5.20.5 (the lastest stable) on Gentoo, Plasma's network load system monior doesn't show any traffic if using a network bridge. IIRC, in some older version, one could select the network device to be monitored. Now, only "Upload rate" and "Download rate" can be added to the chart, and it stays at 0, no matter what passes through my network bridge (eth0 and tap0).
I don't know if this is the same or separate bug, but my system monitor doesn't show any traffic line in network history. Before Plasma 5.21 it was working normally. Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-MANJARO OS Type: 64-bit Graphics Platform: X11
It doesn't measure anything even if you don't have a bridge. 5.19 worked fine, 5.20 is broken. Tried with Deian Bullseye, and Fedora 33.
KSysGuard doesn’t show me Internet graph, while at the same time plasma-systemmonitor shows upload and download. https://i.imgur.com/zxeCg8s.png
I see this also for non-bridge devices on Plasma 5.20.5 (Fedora 33). Network monitor shows no textual or graphic transfer rates. $ ifconfig enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::af0c:****:****:**** prefixlen 64 scopeid 0x20<link> ether xxxxxx txqueuelen 1000 (Ethernet) $ solid-hardware5 nonportableinfo '/org/kde/solid/udev/.../net/enp5s0' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:01.0/0000:05:00.0/net/enp5s0' DEVPATH = '/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:01.0/0000:05:00.0/net/enp5s0' (string) ID_BUS = 'pci' (string) ID_MM_CANDIDATE = '1' (string) ID_MODEL_FROM_DATABASE = 'I211 Gigabit Network Connection' (string) ID_MODEL_ID = '0x1539' (string) ID_NET_DRIVER = 'igb' (string) ID_NET_LINK_FILE = '/usr/lib/systemd/network/99-default.link' (string) ID_NET_NAME_MAC = 'enx7085cxxxxxx' (string) ID_NET_NAME_PATH = 'enp5s0' (string) ID_NET_NAMING_SCHEME = 'v245' (string) ID_OUI_FROM_DATABASE = 'ASRock Incorporation' (string) ID_PATH = 'pci-0000:05:00.0' (string) ID_PATH_TAG = 'pci-0000_05_00_0' (string) ID_PCI_CLASS_FROM_DATABASE = 'Network controller' (string) ID_PCI_SUBCLASS_FROM_DATABASE = 'Ethernet controller' (string) ID_VENDOR_FROM_DATABASE = 'Intel Corporation' (string) ID_VENDOR_ID = '0x8086' (string) IFINDEX = '2' (string) INTERFACE = 'enp5s0' (string) SUBSYSTEM = 'net' (string) SYSTEMD_ALIAS = '/sys/subsystem/net/devices/enp5s0' (string) TAGS = ':systemd:' (string) USEC_INITIALIZED = '7198612' (string)
> Using Plasma 5.20.5 (the lastest stable) on Gentoo, Plasma's network load system monior doesn't show any traffic if using a network bridge. IIRC, in some older version, one could select the network device to be monitored. Now, only "Upload rate" and "Download rate" can be added to the chart, and it stays at 0, no matter what passes through my network bridge (eth0 and tap0). Do you use network manager? If you do, we currently intentionally filter out anything that is not a physical device, because we want to exclude things like docker containers which aren't all that useful to show. That said, eth0 should still show up. If you don't, we have a backend that uses kernel interfaces for this, but it was added with Plasma 5.21 so please make sure you are running at least that version. We also filter out any device that is not marked as "ETHER" in that backend, which may exclude bridges as well.
I don't use NetworkManager. Plasma 5.21.4 is in Portage, so I'll (try to) upgrade and check if this fixes the isse. Thanks for the Info!
Yes, I use network manager. This is on Fedora 33, Plasma 5.20.5. nmcli shows one physical (wired) connection: $ nmcli device DEVICE TYPE STATE CONNECTION enp5s0 ethernet connected Wired connection 1 docker0 bridge connected (externally) docker0 br-88e9fca1b449 bridge connected (externally) br-88e9fca1b449 virbr0 bridge connected (externally) virbr0 knemo is able to show statistics for the enp5s0 device, but Network System Monitor shows no devices.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I don't use docker containers or anything unusual. Only cable modem and Manjaro desktop. I didn't change modem configuration. After Plasma update it just stopped working.
*** Bug 437840 has been marked as a duplicate of this bug. ***
Okay, so, although after the upgrade to Plasma 5.21.5, the start menu looks a bit spooky ;-) the issue with the network manager seems to be gone. I do get upload and download rates again for my setup with a bridge.
Problem still exist on Manjaro 5.21.5
I think we deal with two separate issues here : a) bridge traffic is not included in device unspecific rates b) the bridge is not selectable as network device for specific device rates
Actually, I only can select all ingoing and outgoing traffic ("Upload Rate"/"Download Rate"), not a specific device. Anyway, the traffic is shown again. Would surely be way nicer to be able to select the traffic for a very device though ...
It appeared that on one Manjaro installation it works ok when cable is attached to motherboard. But on other installation (the same motherboard but separate disk) regardless of where cable is attached to motherboard or PCI internet card there is no graph. But I don't know what else to check. I reinstalled ksysguard but no results. Is it a configuration issue?
This solution worked for me https://bbs.archlinux.org/viewtopic.php?id=224215 Copy the default “SystemLoad2.sgrd” file from /usr/share/ksysguard/ to ~/.local/share/ksysguard/ I already had this file so I overwritten it and it works.
Removing ~/.local/share/ksysguard/ did not fix the issue for me.
Maybe that is the problem that configuration files in ~/.local/share/ksysguard/ are not created / updated properly when files in /usr/share/ksysguard/ are created / replaced by a new version. @miklos This would explain my situation when I had this file but it didn't work properly until I replaced it with a new one from /usr/share/ksysguard/ Did your system create files in ~/.local/share/ksysguard/ after you had removed old ones? Did you try coping from /usr/share/ksysguard/
@apache The system did not create files in ~/.local/share/ksysguard/ after I removed old ones. I tried coping the stuff there from /usr/share/ksysguard/, but it didn't help.
For whatever reason, despite of 5.22.1 being installed, the monior stopped working again (maybe due to a reboot or whatever?!) I don't even have ksysguard installed (also not when it worked in the meantime), so that should not trigger it.
I upgraded to Fedora 34, and got plasma-workspace 5.22.2. The network monitor is working now, let's hope it stays that way. However, for example, Debian Bullseye is going to be released soon, and it will be stuck with plasma 5.20.5 for a very very long time.
Now I upgraded my Debian machine after the Bullseye release, so I have Plasma 5.23.2 now. The network monitor doesn't work. All the other systemmonitor widgets work properly.