Bug 48980

Summary: kmail leaves child process running on exit, can't restart kmail
Product: [Unmaintained] kmail Reporter: Glen Barney <glen>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: 1.4.3   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Glen Barney 2002-10-10 20:03:07 UTC 
Version:           1.4.3 (using KDE KDE 3.0.3)
Installed from:    SuSE RPMs
OS:          Linux

On a newly-installed Suse Linux 8.1 system with KDE 3.0.3 and KMail 1.4.3, KMail fails to shut down correctly on exit.  Whether I exit with the "X" box or through the File menu, a child KMail process continues running on my server.

Compact-Folders-On-Exit is DISABLED, so this is not related to those bugs.

This occurs whether I check mail or not, so this is not related to the POP process bugs.

Even if I just start KMail, and immediately quit, the process stays there.  The process is killable using killall, or the normal signal 15 kill, and it does not appear to use any CPU time, it just sits there... but because it's there, KMail cannot be restarted until that process is killed.

I notice that kdeinit is leaving phantom kio_pop3 and kio_smtp processes around, too, but even if there are no such processes, KMail's child still lives on.
Comment 1 Ingo Klöcker 2002-10-11 00:24:41 UTC 
Subject: Re:  New: kmail leaves child process running on exit, can't restart kmail

On Thursday 10 October 2002 20:03, Glen Barney wrote:
> Even if I just start KMail, and immediately quit, the process stays
> there.  The process is killable using killall, or the normal signal
> 15 kill, and it does not appear to use any CPU time, it just sits
> there... but because it's there, KMail cannot be restarted until that
> process is killed.

Please kill KMail with 'killall -6 kmail'. You should get a backtrace. 
Please send us this backtrace.

Anyway, I never had this behaviour on SuSE 8.0. Maybe the SuSE 8.1 
packages are broken. Or this problem is gcc 3.2 related.

Regards,
Ingo
Comment 2 Ingo Klöcker 2002-10-20 00:48:47 UTC 
Subject: Re:  kmail leaves child process running on exit, can't restart kmail

On Friday 11 October 2002 00:35, Glen wrote:
> #6  0x41423f2e in select () from /lib/libc.so.6
> #7  0x410e0978 in typeinfo for QMotifStyle () from
> /usr/lib/libqt-mt.so.3

Which widget style are you using? If you are not using the HighColor 
style could you then please select this style and test whether KMail 
still hangs on exit.

> Even after this backtrace runs, there are still many related
> processes still in the table, even though KMail has died:

Don't worry about those processes. They will die automatically after a 
timeout.

Regards,
Ingo
Comment 3 Glen Barney 2002-10-20 05:44:12 UTC 
Subject: Re:  kmail leaves child process running on exit, can't restart kmail

        Which widget style are you using? If you are not using the HighColor
        style could you then please select this style and test whether KMail
        still hangs on exit.

I was already using that style, sorry!  It still hangs on exit.

Glen
Comment 4 Fabian 2002-11-07 05:08:23 UTC 
I have the same problem with a Standard Mandrake 9 install using KMail 1.4.3. 
As well as the process not dying, there are a huge number of pop and smtp
processes running, that get to the point where it slows my machine down to a
crawl.  I have had up to 30 pop processes sitting there taking up memory. I have
to then go in an kill them all manually, and my machine becomes responsive
again. This even happens if I use KMail in Icewm instead of KDE.  These
processes don't seem to die even when I exit Kmail (and kill off this errant
process that won't die)
Comment 5 Stephan Kulow 2003-04-13 22:26:17 UTC 
hmm, most likely these are either installation problems or are fixed 
meanwhile. If you're still having the problem with KDE 3.1.1, let us 
know. The killall -6 output would still be interesting I guess.