Bug 112024 - Starting KMail when a lock file exists fails
Summary: Starting KMail when a lock file exists fails
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.8.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-04 12:24 UTC by Anders E. Andersen
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Anders E. Andersen 2005-09-04 12:24:11 UTC 
Version:           1.8.2 (using KDE 3.4.2, Debian Package 4:3.4.2-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12.3

When starting KMail after a crash. KMail will present a dialog telling the user that kmail seems to be running already. You can then choose whether to start KMail anyway or to interupt the startup.

If you select to start KMail the lock file is deleted but KMail does not start.

You can start KMail again and it will start up normally, since the lock fine is now gone.
Comment 1 Anders E. Andersen 2005-09-04 12:25:13 UTC 
See also bug #86516. Not the same bug but somewhat related.
Comment 2 Thiago Macieira 2005-09-04 13:38:25 UTC 
Can you check if KMail 1.9 alpha (from KDE 3.5 alpha) works? I think this has been fixed.
Comment 3 Anders E. Andersen 2005-09-04 14:20:11 UTC 
Not easily. I use debian unstable and I don't quite have the hang of compiling the entire kde myself. I guess I could try to extract the kmail package from the other source and compile it alone maybe. I'll give it a shot.
Comment 4 Anders E. Andersen 2006-01-09 10:43:07 UTC 
Just updating.. KDE 3.5 has entered Debian Unstable. I will keep an eye on this.
Comment 5 Anders E. Andersen 2006-02-14 18:42:39 UTC 
It seems this bug is fixed in 3.5.

Closing.