Bug 424270 - Quitting KSysGuard via window button or menu item causes org.kde.ksysguard.plugin.network errors, sometimes coredump
Summary: Quitting KSysGuard via window button or menu item causes org.kde.ksysguard.pl...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (other bugs)
Version First Reported In: 5.18.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-16 03:21 UTC by Stephen Peterson
Modified: 2024-09-23 21:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Peterson 2020-07-16 03:21:51 UTC 
SUMMARY
Quitting KSysGuard via window button or menu item causes org.kde.ksysguard.plugin.network errors, sometimes coredump

STEPS TO REPRODUCE
1. Run ksysguard from console to see output (either `ksysguard` or `kstart5 ksysguard`)
2. Quit ksysguard using the window button, File > Quit option, or Ctrl+Q hotkey

OBSERVED RESULT
Error messages in console: 
> QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/libexec/ksysguard/ksgrd_network_helper") is still running.
> org.kde.ksysguard.plugin.network: Helper process terminated abnormally!
> org.kde.ksysguard.plugin.network: ""

Sometimes, ksysguard dumps core, but I can't reliably reproduce this behavior.

EXPECTED RESULT
Quitting the application by these standard methods should not produce errors.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Comment 1 Christoph Feck 2020-08-03 18:41:01 UTC 
The crash probably is bug 350140.
Comment 2 Christoph Cullmann 2024-09-23 21:00:17 UTC 
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!