Bug 174376 - kontact/kmail crash at quit after email received
Summary: kontact/kmail crash at quit after email received
Status: RESOLVED DUPLICATE of bug 163712
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-05 21:42 UTC by Kevin Hunter
Modified: 2008-11-05 22:24 UTC (History)
0 users

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

Attachments
Backtrace after crash (2.70 KB, text/plain)
2008-11-05 21:44 UTC, Kevin Hunter 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Hunter 2008-11-05 21:42:21 UTC 
Version:           1.3 (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Basically, it seems that if KMail (as used through Kontact) receives an email, and user quits via File menu, Kontact crashes.

Steps to reproduce:
0. Use KDE 4.1.2 or devel ...
1. Start Kontact fresh (mine starts to summary pane)
2. Click new message button
3. Send yourself a message. Subject/Body optional
4. Click on Mail
5. Receive mail you just sent to yourself.
6. When it arrives (notifies me by sound), quit via File->Quit

Bam, crash.

Note that I don't even open/read the email.  I just quit.
Comment 1 Kevin Hunter 2008-11-05 21:44:07 UTC 
Created attachment 28347 [details]
Backtrace after crash
Comment 2 Kevin Hunter 2008-11-05 21:45:28 UTC 
If it matters, I'm using Kubuntu Intrepid Ibex (8.10), with KDE4.1 stuffs.
Comment 3 Kevin Hunter 2008-11-05 21:46:10 UTC 
If it matters, I'm using the AMD64 version of Kubuntu Intrepid Ibex (8.10), with KDE4.1 stuffs.
Comment 4 Kevin Hunter 2008-11-05 22:17:17 UTC 
I suppose it may be pertinent that I have only one email account setup.  It is IMAP over SSL with clear-text authentication.  In short:

IMAP
SSL
Clear text authentication
Comment 5 Thomas McGuire 2008-11-05 22:24:39 UTC 

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