Summary: | kmail crash while syncing | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Martin Bednar <martin+kde> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | heiko.becker, kdenis |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Martin Bednar
2016-08-16 17:59:00 UTC
Created attachment 100728 [details]
New crash information added by DrKonqi
kmail (5.3.0 (QtWebEngine)) using Qt 5.7.0
- What I was doing when the application crashed:
I get the same backtrace when deleting a mail from a thread which isn't the first one in the thread. Doesn't happen every time, but almost every time.
Version is 16.08.0/5.3.0
-- Backtrace (Reduced):
#6 0x00007efd2c3a6e70 in Akonadi::MessageStatus::toQInt32() const () from /usr/x86_64-pc-linux-gnu/lib64/libKF5AkonadiMime.so.5
#7 0x00007efd2cfadc06 in MessageList::Core::ModelPrivate::attachMessageToParent(MessageList::Core::Item*, MessageList::Core::MessageItem*, MessageList::Core::ModelPrivate::AttachOptions) () from /usr/x86_64-pc-linux-gnu/lib64/libKF5MessageList.so.5
#8 0x00007efd2cfaf191 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass2(MessageList::Core::ViewItemJob*, QElapsedTimer const&) () from /usr/x86_64-pc-linux-gnu/lib64/libKF5MessageList.so.5
#9 0x00007efd2cfb1334 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJob(MessageList::Core::ViewItemJob*, QElapsedTimer const&) () from /usr/x86_64-pc-linux-gnu/lib64/libKF5MessageList.so.5
#10 0x00007efd2cfb1823 in MessageList::Core::ModelPrivate::viewItemJobStepInternal() () from /usr/x86_64-pc-linux-gnu/lib64/libKF5MessageList.so.5
That is possible, I had pressed delete on something befoore it crashed (I distinctly remember because it was an accident). *** This bug has been marked as a duplicate of bug 364994 *** |