Bug 357523

Summary: Kate does not terminate when it's window is closed.
Product: [Applications] kate Reporter: Paul <pip.kde>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: fkoch1980, kare.sars
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Paul 2016-01-04 15:40:14 UTC 
When kate is "terminated" by closing it's window there is a kate process left.

Reproducible: Always

Steps to Reproduce:
1. Launch kate
2. Close kate's window
3. Issue "ps -ef | grep kate" from a vt

Actual Results:  
There is a kate process still shown, for example:
paul@Orion-Tumble:~$ ps -ef | grep kate
paul      1573  1451 10 15:10 ?        00:00:00 /usr/bin/kate -b
paul      1604  1580  0 15:11 pts/0    00:00:00 grep --color=auto kate
paul@Orion-Tumble:~$


Expected Results:  
The kate process terminates when it's window is closed.

This behaviour was observed after the kde-frameworks-5.17.0 update.

Kate 15.08.3
KDE Frameworks 5.17.0
Qt 5.5.1 (built against 5.5.1)

Further information on the openSUSE forum, please see:
https://forums.opensuse.org/showthread.php/512463-Odd-problem-with-%28kde%29-kate-following-the-20151229-TW-snapshot
Comment 1 FrankRep 2016-01-04 15:45:10 UTC 
I have the same problem.

When I close the Kate window, Kate process is still running in the background yet the window is gone. When I go to open another file associated with Kate, it opens in the background process and no window is displayed. 

I have to use "killall kate" to remove the processes from the background in order to use Kate again.

- Fedora 22
- Kate Version 5.0.0

Using:
KDE Frameworks 5.17.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system
Comment 2 Paul 2016-01-04 15:48:09 UTC 
Sorry, forgot to add if I use "File -> Quit" instead of the "Close" button, kate terminates correctly.
Comment 3 FrankRep 2016-01-04 15:54:25 UTC 
Confirmed:

"File -> Quit" properly terminates Kate. 

The "Close" button is causing the problem.
Comment 4 Kåre Särs 2016-01-05 07:18:56 UTC 

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