Created attachment 135488 [details] context from journalctl SUMMARY I have a weird problem with my nic which I believe causes ksysguard to crash. STEPS TO REPRODUCE 1. sometimes, my network stops working. 2. This causes network manager to first come in "Limited connectivity" state (first line in attached logs) 3. after that i usually unplug the network cable to see if it helps OBSERVED RESULT segfault something like this (more context in attachment): feb 07 18:23:33 laptop kernel: ksystemstats[2631]: segfault at 55fe2af48a1d ip 00007fddd79c545b sp 00007fff08b58a50 error 4 in libksgrdbackend.so[7fddd79c4000+5000] feb 07 18:23:33 laptop kernel: Code: d0 eb 0d 0f 1f 40 00 48 83 c0 08 48 39 c8 74 0b 48 8b 10 48 39 d5 74 ef 48 89 d5 48 8b 75 18 4c 8d 7c 24 10 4c 89 ff 48 8b 06 <ff> 50 70 48 89 ef e8 da ee ff ff 48 89 c5 49 3b 86 88 00 00 00 0f EXPECTED RESULT no segfault SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse tumbleweed 20210128 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have a quite recent laptop model: Dell Latitude 5501. Network is problematic, even on windows I sometimes have to unplug / replug the cable to regain network access. Still, I believe ksysguard should not crash..?
Same segfault on Debian stable with kded5 5.78.0: ksystemstats[11801]: segfault at 70 ip 00007f619b12251b sp 00007fff116cc970 error 4 in libksgrdbackend.so[7f619b121000+5000] No flaky network or anything like that. Seems to occur more often when hibernating or resuming from hibernation. So far had one oom-killer kill ksystemstats (possibly unrelated?).
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task. If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!