Summary: | kontact,crash during launching | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Philippe ROUBACH <philippe.roubach> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | aroth |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.12.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Philippe ROUBACH
2014-02-03 09:44:53 UTC
Created attachment 86029 [details]
New crash information added by DrKonqi
kontact (4.13 rc) on KDE Platform 4.12.97 using Qt 4.8.6
- What I was doing when the application crashed:
migration to kde 4.12.97:
about 3 or four identical prompts appeared for migrating knotes content.
and 3 kontact instances were started. While closing two of them, I got the crash
-- Backtrace (Reduced):
#6 0x00007f65fe654951 in MailCommon::Util::updatedCollection (col=...) at ../../mailcommon/util/mailutil.cpp:610
#7 0x00007f65fea2f313 in KMMainWidget::updateMessageActionsDelayed (this=this@entry=0x3c5fc00) at ../../kmail/kmmainwidget.cpp:3969
#8 0x00007f65fea2fc9b in KMMainWidget::updateMessageActions (this=this@entry=0x3c5fc00, fast=fast@entry=false) at ../../kmail/kmmainwidget.cpp:3809
#9 0x00007f65fea30a0a in KMMainWidget::initializeFilterActions (this=0x3c5fc00) at ../../kmail/kmmainwidget.cpp:4317
#10 0x00007f65fedb5e49 in KMailPart::guiActivateEvent (this=0x269eac0, e=0x7fff1e923b90) at ../../kmail/kmail_part.cpp:159
*** Bug 333684 has been marked as a duplicate of this bug. *** This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |