SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** History view in System Monitor does not show network activity under "Network" and there seems no way to point System Monitor to the correct interface. STEPS TO REPRODUCE 1. start System Monitor as window on desktop 2. switch to History view 3. OBSERVED RESULT "CPU" and "Memory" load are shown but "Network" is void EXPECTED RESULT I'd expect a means to see and adjust which network interface is monitored network activity ought to be shown (up and down) as was with earlier versions of System Monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.14.0-3-amd64 #1 SMP Debian 5.14.12-1 (2021-10-14) x86_64 GNU/Linux (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Graphics: X11 My personal opinion: System Monitor GUID has been changed without any advantage whatsoever - even making it worse because now it's less informative.
Hmm, works for me for my simple use case of one wifi interface. Do you have an unusual network setup or multiple active interfaces?
Created attachment 144554 [details] attachment-23971-0.html On Dienstag, 14. Dezember 2021 16:34:43 -03 Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=446933 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------- > ------ CC| |nate@kde.org Resolution|--- > |WAITINGFORINFO Status|REPORTED > |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Hmm, works for me for my simple use case of one wifi interface. > > Do you have an unusual network setup or multiple active interfaces? I don't think that this is unusual but what do I know... :*~*# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 78:24:af:37:6d:60 brd ff:ff:ff:ff:ff:ff inet 192.168.12.21/24 brd 192.168.12.255 scope global enp3s0 valid_lft forever preferred_lft forever inet6 2001:470:7075:e2:7a24:afff:fe37:6d60/64 scope global dynamic mngtmpaddr valid_lft 2591911sec preferred_lft 604711sec inet6 fe80::7a24:afff:fe37:6d60/64 scope link valid_lft forever preferred_lft forever 3: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff Thank you for looking into this Greetings Eike
Created attachment 144555 [details] attachment-27550-0.html On Dienstag, 14. Dezember 2021 16:34:43 -03 Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=446933 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------- > ------ CC| |nate@kde.org Resolution|--- > |WAITINGFORINFO Status|REPORTED > |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Hmm, works for me for my simple use case of one wifi interface. > > Do you have an unusual network setup or multiple active interfaces? Tried it on a virtual Bookworm installation with vanilla KDE root@sid-vm:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 08:00:27:94:a6:d9 brd ff:ff:ff:ff:ff:ff inet 192.168.12.33/24 brd 192.168.12.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2001:470:7075:e2::33/48 scope global valid_lft forever preferred_lft forever inet6 fe80::a00:27ff:fe94:a6d9/64 scope link valid_lft forever preferred_lft forever and also zilch - nothing - nada ... Where can I look to analyze the problem? Any wheels to turn or config files to adjust? Cheers Eike
I wish I knew. ksystemstats is clearly running since *some* graphs work. The System Monitor developers will have to take over from here.
Created attachment 144560 [details] attachment-7236-0.html On Dienstag, 14. Dezember 2021 16:34:43 -03 Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=446933 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------- > ------ CC| |nate@kde.org Resolution|--- > |WAITINGFORINFO Status|REPORTED > |NEEDSINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Hmm, works for me for my simple use case of one wifi interface. > > Do you have an unusual network setup or multiple active interfaces? Does SystemLoad2.sdrg have something to do with it? <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE KSysGuardWorkSheet> <WorkSheet locked="1" title="System Load" interval="0.5" columns="1" rows="3"> <host command="ksysguardd" name="localhost" port="-1" shell=""/> <display rowSpan="1" row="0" vLines="0" hLines="1" vScroll="0" unit="" version="1" manualRange="0" svgBackground="widg ets/plot-background" vDistance="30" column="0" hScale="6" autoRange="0" labels="1" fontSize="8" columnSpan="1" title="C PU History" showUnit="0" stacked="0" class="FancyPlotter"> <beam regexpSensorName="cpu/cpu.*/TotalLoad" sensorType="float" color="0xffff8000,0xffe20800,0xfff3c300,0xffff55ff" h ostName="localhost"/> </display> <display rowSpan="1" row="1" vLines="0" hLines="1" vScroll="0" unit="" version="1" manualRange="0" svgBackground="widg ets/plot-background" vDistance="30" column="0" hScale="6" autoRange="0" labels="1" fontSize="8" columnSpan="1" title="M emory and Swap History" showUnit="0" stacked="0" class="FancyPlotter"> <beam sensorName="mem/physical/application" sensorType="integer" color="0xffc000c0" hostName="localhost" summationNam e="Memory"/> <beam sensorName="mem/swap/used" sensorType="integer" color="0xff00c000" hostName="localhost" summationName="Swap"/> </display> <display rowSpan="1" row="2" vLines="0" hLines="1" vScroll="0" unit="" version="1" min="0" manualRange="1" svgBackgrou nd="widgets/plot-background" vDistance="30" column="0" hScale="6" autoRange="1" labels="1" fontSize="8" columnSpan="1" title="Network History" showUnit="0" stacked="0" max="20" class="FancyPlotter"> <beam regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/receiver/ data" sensorType="float" color="0xffb3 a52d" hostName="localhost" summationName="Receiving"/> <beam regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/transmitter/ data" sensorType="float" color="0xf f844798" hostName="localhost" summationName="Sending"/> </display> </WorkSheet> Unfortunately I don't know which values might be valid for "network/interfaces/(?!lo|bridge|usbus|bond).
I believe 5.23 didn't yet have the fallback for when NetworkManager isn't running. This has been implemented in the meantime, so I think this is fixed at this point.
On Friday, 7 June 2024 07:43:29 -04 Arjen Hiemstra wrote: > https://bugs.kde.org/show_bug.cgi?id=446933 > > Arjen Hiemstra <ahiemstra@heimr.nl> changed: > > What |Removed |Added > ---------------------------------------------------------------------- > ------ Status|REPORTED |RESOLVED > Resolution|--- |FIXED > > --- Comment #6 from Arjen Hiemstra <ahiemstra@heimr.nl> --- > I believe 5.23 didn't yet have the fallback for when NetworkManager > isn't running. This has been implemented in the meantime, so I think > this is fixed at this point. High! Don't know if this is related but I had the network activity missing in system monitor too. It happened years ago and recently after updates happened again. In both cases until I deinstalled NetworkManager, then the network activity showed again. NM uses to come back via updates and needs to be apt purged again. I'm using static IPs on my desktop PC. Kind regards -- Eike Lantzsch KY4PZ / ZP5CGE