Bug 1613644 - KMail crashes with SIGSEV
Summary: KMail crashes with SIGSEV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kmail
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-08 04:25 UTC by kevin
Modified: 2019-05-28 22:05 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:05:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output from gdb (22.24 KB, text/plain)
2018-08-08 04:25 UTC, kevin
no flags Details

Description kevin 2018-08-08 04:25:00 UTC
Created attachment 1474146 [details]
output from gdb

Description of problem:
KDE crashes when opening with a new received message containing multiple attachments

Version-Release number of selected component (if applicable):
$ kmail --version
kmail2 5.7.3

How reproducible:
This is a hard error

Steps to Reproduce:
Unsure

Actual results:
SIGSEV

Comment 1 Rex Dieter 2018-08-08 14:01:24 UTC
Thread 1 "kmail" received signal SIGSEGV, Segmentation fault.
0x00007fffecfcb7df in KContacts::Addressee::Addressee(KContacts::Addressee const&) () from /lib64/libKF5Contacts.so.5
(gdb) bt
#0  0x00007fffecfcb7df in KContacts::Addressee::Addressee(KContacts::Addressee const&) () from /lib64/libKF5Contacts.so.5
#1  0x00007fff191448b0 in MessageViewer::VcardMemento::address(int) const () from /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_text_vcard.so
#2  0x00007fff1914250e in (anonymous namespace)::Formatter::render(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*, MessageViewer::RenderContext*) const ()
   from /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_text_vcard.so
#3  0x00007ffff0178443 in MimeTreeParser::DefaultRendererPrivate::renderWithFactory(QMetaObject const*, QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#4  0x00007ffff017cfd1 in MimeTreeParser::DefaultRendererPrivate::renderFactory(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#5  0x00007ffff017dccb in MimeTreeParser::DefaultRendererPrivate::renderSubParts(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#6  0x00007ffff01781c6 in MimeTreeParser::DefaultRendererPrivate::render(QSharedPointer<MimeTreeParser::MimeMessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#7  0x00007ffff017d20e in MimeTreeParser::DefaultRendererPrivate::renderFactory(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#8  0x00007ffff017dccb in MimeTreeParser::DefaultRendererPrivate::renderSubParts(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#9  0x00007ffff0177f77 in MimeTreeParser::DefaultRendererPrivate::render(QSharedPointer<MimeTreeParser::MessagePartList> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#10 0x00007ffff017d0c5 in MimeTreeParser::DefaultRendererPrivate::renderFactory(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#11 0x00007ffff017dbc2 in MimeTreeParser::DefaultRendererPrivate::DefaultRendererPrivate(QSharedPointer<MimeTreeParser::MessagePart> const&, MessageViewer::CSSHelperBase*, MimeTreeParser::HtmlWriter*, MessageViewer::MessagePartRendererFactory const*) () from /lib64/libKF5MessageViewer.so.5
#12 0x00007ffff017dc27 in MessageViewer::DefaultRenderer::DefaultRenderer(QSharedPointer<MimeTreeParser::MessagePart> const&, MessageViewer::CSSHelperBase*, MimeTreeParser::HtmlWriter*) ()
   from /lib64/libKF5MessageViewer.so.5
#13 0x00007ffff01a0e5f in MessageViewer::MailViewerSource::render(QSharedPointer<MimeTreeParser::MessagePart> const&, MimeTreeParser::HtmlWriter*) () from /lib64/libKF5MessageViewer.so.5
#14 0x00007fffedeb0a6e in MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*) () from /lib64/libKF5MimeTreeParser.so.5
#15 0x00007ffff01b2509 in MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from /lib64/libKF5MessageViewer.so.5
#16 0x00007ffff01b2a40 in MessageViewer::ViewerPrivate::displayMessage() () from /lib64/libKF5MessageViewer.so.5
#17 0x00007ffff01b34eb in MessageViewer::ViewerPrivate::updateReaderWin() () from /lib64/libKF5MessageViewer.so.5
#18 0x00007ffff3346de3 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#19 0x00007ffff3352e1b in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5
#20 0x00007ffff33479db in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#21 0x00007ffff3be5e95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#22 0x00007ffff3bed83a in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#23 0x00007ffff331e376 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#24 0x00007ffff336df19 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5
#25 0x00007ffff336e7bc in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#26 0x00007fffde4198ad in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#27 0x00007fffde419c78 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#28 0x00007fffde419d10 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#29 0x00007ffff336ec13 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#30 0x00007fffc34d2065 in QPAEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5XcbQpa.so.5
#31 0x00007ffff331d12b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#32 0x00007ffff33255b6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
---Type <return> to continue, or q <return> to quit---
#33 0x000055555555799f in main ()


That's a start, but unfortunately, it's missing debuginfo and doesn't include all threads (which may be relevant).  To fix:

dnf debuginfo-install kmail

and then generate backtrace using:
thread apply all bt
(instead of just 'bt')

Then ideally, this would be reported upstream to bugs.kde.org if that's possible for you.  otherwise, I'll do my best to get upstream eyes here.

Comment 2 kevin 2018-08-08 23:14:34 UTC
1) I have done as requested re gdb
2) I have opened Bug 397290 with KDE
3) Please close this bug report

BTW: The reason that I reported it here was because I thought that Fedora may have made it's own changes to KDE / Kmail. Does this ever happen? If so, how can I tell in any specific case?

Comment 3 Ben Cotton 2019-05-02 19:17:04 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-02 21:10:59 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-05-28 22:05:05 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.