Bug 192596 - kmail lock file remains after shutdown and causes problems for restart
Summary: kmail lock file remains after shutdown and causes problems for restart
Status: RESOLVED DUPLICATE of bug 143187
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.11.2
Platform: unspecified Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2009-05-13 20:32 UTC by Praedor Tempus
Modified: 2010-02-28 00:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Praedor Tempus 2009-05-13 20:32:48 UTC
Version:           1.11.2 (using 4.2.2 (KDE 4.2.2), Mandriva Linux release 2009.1 (Cooker) for i586)
Compiler:          gcc
OS:                Linux (i686) release

I always run kontact.  I have kde set to restart any apps I have running when I shutdown.  When I restart/relogin, kmail keeps producing an error message warning that another instance of kmail appears to be running and to not start kmail unless I am certain another instance is not running.  It is NOT running, it is a fresh login or startup - it SHOULD simply be restarting.  If I elect not to start kmail, then no kmail starts at all.  If I go ahead and start kmail, I then get two instances of kmail at the same time.  Shutting down one brings down both.  I have since found that no matter what I do, upon login/restart, a lock file remains in the ~/.kde4/share/apps/kmail directory regardless of whether or not I shutdown or logged out properly.
Comment 1 Jaime Torres 2009-05-14 13:00:18 UTC
Very related to bugs 188067, 187023, 189512.
Comment 2 Fabio Rossi 2010-01-05 00:16:12 UTC
Yes, I can confirm the problem. This bug is really annoying at startup, I have to close kontact and restart it very often.
Comment 3 Fabio Rossi 2010-01-05 00:17:43 UTC
I forgot to say I'm using

Qt: 4.5.3
KDE: 4.3.4 (KDE 4.3.4)
KMail: 1.12.4
Comment 4 Björn Ruberg 2010-02-28 00:33:55 UTC

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