Bug 116764

Summary: leaves process behind when quitting
Product: [Unmaintained] knode Reporter: JW <jw203198>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description JW 2005-11-20 13:35:22 UTC 
Version:           0.9.0 (using KDE KDE 3.4.0)
Installed from:    Compiled From Sources
Compiler:          gcc n/a
OS:                Linux

If you run knode on remote X server it opens up a host of unnecssary processes.  For example it decides to play sound on localhost (but is displaying on a remote desktop!). It also starts up lots of totally unnecessary processes, like dcopserver, kdeinit, klauncher, kded, gam_server, etc and there doesnt seem to be a way to stop them.

Worse still, when you close knode it keeps running as a zombie. You have to do a ps and kill it manually.

You guys should try running knode on something like X-Win32 and see what a messy conglomeration of kde processes start up and never go away unless you kill them manually.

BTW there also seems to be no way to stop spelling check in knode.
And it is about 3 times slower than previous version.
Comment 1 Thiago Macieira 2005-11-20 15:21:40 UTC 
There's nothing to be done for the extra processes (kdeinit, klauncher, dcopserver, etc.). They WILL be launched, period.

But knode shouldn't keep running after you quit it.
Comment 2 Volker Krause 2005-11-20 15:38:13 UTC 
The bug that KNode keeps running on some systems (#77381) has been fixed in KDE 3.4.1. The extra processes are necessary (and not limited to KNode), but they quit as soon as KNode has exited.

*** This bug has been marked as a duplicate of 77381 ***