Bug 167875

Summary: "kopete" process keeps running after exiting Kopete
Product: [Unmaintained] kopete Reporter: Damien Gombault <desintegr>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: fhimpe, torquil
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Damien Gombault 2008-07-31 18:36:02 UTC 
Version:            (using KDE 4.1.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

"kopete" process keeps running after exiting Kopete and cause some problems.

How to reproduce :
 - run Kopete (from Krunner or Kickoff)
 - quit Kopete with File/Quit
 - it will close the main Kopete window and close the system tray icon, but the "kopete" process is still running. You can check with KSysGuard or "ps -A | grep kopete".

If you run Kopete again, the system tray icon does not appear and it's impossible to exit Kopete : File/Quit will do nothing. The only way to close it is to send a SIGTERM or SIGKILL signal to the process.

I use Debian lenny with KDE 4.1 experimental packages.
I also have this problem with KDE Four Live OpenSUSE LiveCD.
Comment 1 Damien Gombault 2008-07-31 18:41:14 UTC 
Sorry duplicate of bug #167826.
Comment 2 Roman Jarosz 2008-08-01 22:26:04 UTC 
SVN commit 840788 by rjarosz:

Delete KopeteWindow if we are shutting down otherwise KGlobal::deref() isn't called.

CCBUG: 167875



 M  +6 -1      kopeteapplication.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=840788
Comment 3 Roman Jarosz 2008-08-01 22:31:07 UTC 
SVN commit 840790 by rjarosz:

Backport commit 840788.
Delete KopeteWindow if we are shutting down otherwise KGlobal::deref() isn't called.

CCBUG: 167875



 M  +6 -1      kopeteapplication.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=840790
Comment 4 Roman Jarosz 2008-08-02 15:58:06 UTC 
*** Bug 168104 has been marked as a duplicate of this bug. ***
Comment 5 Roman Jarosz 2008-08-02 20:15:01 UTC 
*** Bug 168120 has been marked as a duplicate of this bug. ***