Bug 185820

Summary:	kMail does not terminate after quitting it
Product:	[Unmaintained] kmail	Reporter:	Gunter Ohrner <kdebugs>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	axel.braun, bjoern, craig.magina, finex, kavol, keplicz
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gunter Ohrner 2009-02-28 19:05:44 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Quitting kMail via the tray icon only closes kMails main window and removes the tray icon, but there's still a kmail instance left running invisibly.

Logging of from KDE in this state causes a kmail crash window to appear (SIGSEGV), stating kmail again in this state also causes a crash window to appear or alternatively "nothing" to happen, but the invisible instance is gone after the failed start attempt.

Comment 1 Craig Magina 2009-03-14 00:34:25 UTC

I am also experiencing this running on Fedora 10, fully updated.  kmail is listed under krunner's system activity using ~180M of ram and is still actually eating CPU cycles.  I also see a kio_file for a kmail socket residing under kdeinit4.  This is on KDE 4.2.0, KMail 1.11.0.  Even using quit from kmail's File menu doesn't remove the thread.  I can still re-open kmail and it opens quickly.  I am using kmail to download e-mail from an Exchange server through imap.  Re-opening it then using File->Quit left a kio_imap4 thread behind as well.

Comment 2 Jaime Torres 2009-04-23 09:57:41 UTC

*** Bug 190331 has been marked as a duplicate of this bug. ***

Comment 3 Piotr Keplicz 2009-11-18 21:51:37 UTC

This bug can be still experienced on KDE 4.3.3 (and earlier 4.3 versions).

After quitting Kontact, there are some processes left:
kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket....
kdeinit4: kio_imap4 [kdeinit] imaps local:/tmp/ksocket....
kdeinit4: kio_pop3 [kdeinit] pop3 local:/tmp/ksocket....

One cannot start Kontact again without "killall kontact" first.

Comment 4 Björn Ruberg 2009-12-29 22:28:24 UTC

Probably there are other duplicates of this. Will try to find them

Comment 5 Björn Ruberg 2009-12-29 22:28:37 UTC

*** Bug 133261 has been marked as a duplicate of this bug. ***

Comment 6 FiNeX 2010-08-16 22:30:32 UTC

I'm not able to reproduce using KDE 4.4.5.

Please reopen if someone is able to reproduce in KDE 4.4.5 or more recent.

Comment 7 kavol 2010-08-17 13:15:50 UTC

(In reply to comment #6)
> I'm not able to reproduce using KDE 4.4.5.
> 
> Please reopen if someone is able to reproduce in KDE 4.4.5 or more recent.

not sure if this is completely fixed ... even after 'kmail' process disappearing, I still have running processes like these:

kavol     9630  9449  0 11:02 ?        00:00:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket local:/tmp/ksocket-kavol/kmailTm9444.slave-socket
kavol     9881  9449  0 13:02 ?        00:00:00 kdeinit4: kio_pop3 [kdeinit] pop3s local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket local:/tmp/ksocket-kavol/kmaillQ9444.slave-socket
kavol     9894  9449  0 13:03 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket local:/tmp/ksocket-kavol/kmailwA9444.slave-socket

- not to mention tons of akonadi/dbus/nepomuk ballast ...

however, I don't have the rights to reopen this