I noticed several crash dumps from ksgrd_network_helper in coredumpctl output. Generated for unknown reason, I had no error indications except these dumps. Versions: Linux Fedora 35 x64 libksysguard-5.23.3-1.fc35.x86_64 qt5-qtbase-5.15.2-28.fc35.x86_64 Output from `coredumpctl info`: PID: 3483 (ksgrd_network_h) UID: 1000 (andrew) GID: 1000 (andrew) Signal: 6 (ABRT) Timestamp: Wed 2021-12-01 12:48:10 EET (36min ago) Command Line: /usr/libexec/ksysguard/ksgrd_network_helper Executable: /usr/libexec/ksysguard/ksgrd_network_helper Control Group: /user.slice/user-1000.slice/session-1.scope Unit: session-1.scope Slice: user-1000.slice Session: 1 Owner UID: 1000 (andrew) Boot ID: 87df8e1cc2d848cbb9824cf0a5437e93 Machine ID: fd77873a77c84da0997728465757fc65 Hostname: localhost Storage: /var/lib/systemd/coredump/core.ksgrd_network_h.1000.87df8e1cc2d848cbb9824cf0a5437e93.3483.1638355690000000.zst (present) Disk Size: 94.8K Message: Process 3483 (ksgrd_network_h) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: 5b7ade7a1e833a0625796ae5543edbee0edfc591 Found module libnl-route-3.so.200 with build-id: 25ac144713fd4d7ed0d9394a7d36c424b185fdf1 Found module ld-linux-x86-64.so.2 with build-id: da6dc8cd9ecc65cbd54815426326bae9614f727c Found module libm.so.6 with build-id: 3277765566c674dc9766f30a8ac41f5a6f7f6ca7 Found module libibverbs.so.1 with build-id: 430c741a2cb0616690ec46b78488a9987c07e6a0 Found module libc.so.6 with build-id: 148792ddec60e0b15e20655fdc10c35a5c394413 Found module libgcc_s.so.1 with build-id: 279c1648ee67377b5de1c45a244740beea48423e Found module libstdc++.so.6 with build-id: ee39599366a0d94a90b4d1b74bd39bb6ce9e4cea Found module libnl-3.so.200 with build-id: 9ec8cd67a8293913423a6e854ed3c21bb97ecf9e Found module libpcap.so.1 with build-id: d2259e63bc0fc951f7cc4d07c02d3b01a16ff76b Found module ksgrd_network_helper with build-id: 2413b388e3f74b97218d1aa33304f1dc293bba8b Stack trace of thread 3489: #0 0x00007f3aa3a0885c __pthread_kill_implementation (libc.so.6 + 0x8f85c) #1 0x00007f3aa39bb6b6 raise (libc.so.6 + 0x426b6) #2 0x00007f3aa39a57d3 abort (libc.so.6 + 0x2c7d3) #3 0x000055c996e825b4 _ZSt20__replacement_assertPKciS0_S0_ (ksgrd_network_helper + 0x65b4) #4 0x000055c996e851cf _ZN17ConnectionMapping4loopEv (ksgrd_network_helper + 0x91cf) #5 0x00007f3aa3c76c84 execute_native_thread_routine (libstdc++.so.6 + 0xd9c84) #6 0x00007f3aa3a06b17 start_thread (libc.so.6 + 0x8db17) #7 0x00007f3aa3a8b6c0 __clone3 (libc.so.6 + 0x1126c0) Stack trace of thread 3483: #0 0x00007f3aa3a0377a __futex_abstimed_wait_common (libc.so.6 + 0x8a77a) #1 0x00007f3aa3a085f4 __pthread_clockjoin_ex (libc.so.6 + 0x8f5f4) #2 0x00007f3aa3c76ec7 _ZNSt6thread4joinEv (libstdc++.so.6 + 0xd9ec7) #3 0x000055c996e820dc _ZNSt23_Sp_counted_ptr_inplaceI17ConnectionMappingSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv (ksgrd_network_helper + 0x60dc) #4 0x000055c996e82247 _ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv (ksgrd_network_helper + 0x6247) #5 0x000055c996e80707 main (ksgrd_network_helper + 0x4707) #6 0x00007f3aa39a6560 __libc_start_call_main (libc.so.6 + 0x2d560) #7 0x00007f3aa39a660c __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d60c) #8 0x000055c996e81a85 _start (ksgrd_network_helper + 0x5a85)
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!