Bug 179511

Summary: Crash after pop-up dialogs in KMail component
Product: [Applications] kontact Reporter: Georg Wittenburg <georg.wittenburg>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Backtrace for 1)
Backtrace for 2)
Backtrace for 3)

Description Georg Wittenburg 2009-01-03 17:53:10 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

I just had several crashes of Kontact 4.1.86 (using unofficial Debian packages from kde42.debian.net version 4:4.1.86+svn902265-0r1):

1) Crash when restarting Kontact after a DIMAP folder was deleted in the previous session. Kontact briefly display a dialog about whether the folder should be deleted on the server, then it crashes. Starting the KMail stand-alone application worked fine and worked around this issue.

2) Crash after confirming the dialog about whether all mails in a folder should be moved to the trash.

3) Crash after confirming the dialog about whether the trash should be emptied.

I'll post the backtraces as attachments to this bug report. They are all quite similar, so maybe there's a single cause to all three crashes. Hence, I'm only opening one bug report; please split up as necessary.
Comment 1 Georg Wittenburg 2009-01-03 17:54:17 UTC 
Created attachment 29866 [details]
Backtrace for 1)
Comment 2 Georg Wittenburg 2009-01-03 17:55:19 UTC 
Created attachment 29867 [details]
Backtrace for 2)
Comment 3 Thomas McGuire 2009-01-03 17:56:55 UTC 
*** Bug 179510 has been marked as a duplicate of this bug. ***
Comment 4 Georg Wittenburg 2009-01-03 17:56:56 UTC 
Created attachment 29868 [details]
Backtrace for 3)
Comment 5 Thomas McGuire 2009-01-03 17:57:01 UTC 
*** Bug 179508 has been marked as a duplicate of this bug. ***
Comment 6 Thomas McGuire 2009-01-03 17:57:06 UTC 
*** Bug 179509 has been marked as a duplicate of this bug. ***
Comment 7 Thomas McGuire 2009-01-03 18:00:30 UTC 
Backtrace 2 and 3 are the same, of bug 174839.
Backtrace 1 is invalid.
Please don't report more than 1 bug per bug report.