Bug 167794

Summary: quitting kate with the window manager cause closing kate's window but it is still running
Product: [Applications] kate Reporter: Carlo Buratto <carlobbo>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Carlo Buratto 2008-07-31 00:39:05 UTC 
Version:           3.1.0 (using KDE 4.1.0)
Installed from:    SuSE RPMs
OS:                Linux

When i quit kate from ctrl+q, file\exit or exit button of the toolbar, kate quit normally.
When i close kate using the button close of the window, the kate's window close, but the process figure to be still active, not zombie and it still occupies memory.
When i start another kate, the previous process don't close yet, so if i close also the last from the window manager, the window closes but i will have two kate still in memory.
A "kill" with SIGQUIT, SIGHUP, SIGTERM to kate closes the processes remained in memory.
I tried with and without plugins, but it shows the same behaviour.
Comment 1 Dario Andres 2008-07-31 00:46:52 UTC 
Version 3.1.0 Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux i686:
I can confirm this bug
Comment 2 Andreas Pakulat 2008-07-31 11:40:04 UTC 
I don't see this with kate and kwin/kde3 here. Which windowmanager are you using?
Comment 3 Matthew Woehlke 2008-07-31 17:42:44 UTC 
I had this problem with *all* KDE apps about a week back, but it's fixed now. I wonder if the fix didn't get backported? (I'm using kwin, desktop effects disabled.)

Carlo/Darío: Does it happen with other KDE apps also?
Comment 4 George Kiagiadakis 2008-07-31 18:12:21 UTC 

*** This bug has been marked as a duplicate of 167826 ***
Comment 5 Carlo Buratto 2008-07-31 21:20:04 UTC 
It happens with kwin kde4.1 and fluxbox