Summary: | KMail crashed upon restart [invalid QTreeWidget::setItemSelected, KMail::FolderView::restoreItemStates, KMail::FolderView::reload, KMMainWidget::readConfig] | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Christopher Yeleighton <giecrilj> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, ghost, itsteen, kdebugs, mathieu.simard.14, zilla901 |
Priority: | NOR | ||
Version: | 4.4.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christopher Yeleighton
2010-10-20 19:48:29 UTC
*** Bug 254782 has been marked as a duplicate of this bug. *** *** Bug 254785 has been marked as a duplicate of this bug. *** *** Bug 254787 has been marked as a duplicate of this bug. *** *** Bug 254789 has been marked as a duplicate of this bug. *** Created attachment 53114 [details]
New crash information added by DrKonqi
The crash usually occurs after some strangeness with an email being downloaded or timing out, starting after this situation will usually cause the problem. Clearing the imap folders from .kde/share/apps/kmail/imap will usually allow kmail/kontact to start normally.
[Comment from a bug triager] This could be related to bug 184324. [Comment from a bug triager] From bug 252425 (workaround included): -- Information about the crash: KMail started to crash every time I start it, see enclosed backtrace. Editing kmailrc so that all occurences of MainFolderViewItemIsExpanded=true are changed to 'false' appears to fix this problem. From bug 252865: -- Information about the crash: Trying to lanch the app. After entering password, the app fail lo lanch properly an crash. *** Bug 252425 has been marked as a duplicate of this bug. *** *** Bug 252865 has been marked as a duplicate of this bug. *** *** Bug 251702 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 184324 *** *** Bug 259812 has been marked as a duplicate of this bug. *** *** Bug 259821 has been marked as a duplicate of this bug. *** *** Bug 259823 has been marked as a duplicate of this bug. *** |