Summary: | kmail crash when deleting attachment | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Erik Quaeghebeur <bugs.kde.org> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | bugs.kde.org |
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
Erik Quaeghebeur
2015-06-19 10:21:10 UTC
Created attachment 95561 [details]
New crash information added by DrKonqi
kmail (4.14.8) on KDE Platform 4.14.8 using Qt 4.8.6
- What I was doing when the application crashed:
I was deleting an attachment of a message.
-- Backtrace (Reduced):
#6 0x000000384e844054 in KMime::Content::parent() const () from /usr/lib64/libkmime.so.4
#7 0x0000003eff69b4ab in MessageViewer::ViewerPrivate::deleteAttachment(KMime::Content*, bool) () from /usr/lib64/libmessageviewer.so.4
#8 0x0000003eff6ade4a in MessageViewer::ViewerPrivate::slotHandleAttachment(int) () from /usr/lib64/libmessageviewer.so.4
#9 0x0000003eff7356f0 in MessageViewer::ViewerPrivate::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libmessageviewer.so.4
[...]
#11 0x000000384319bd1e in QSignalMapper::mapped(int) () from /usr/lib64/qt4/libQtCore.so.4
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input. |