Application: kmail (5.16.0 (20.12.0)) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.3.18-lp152.57-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: I started kmail. I downloaded new mail from the internet provider. In the window that displayed new messages, I clicked on a particular message, which contained a pdf attachment. Other messages with pdf attachments work fine. - Custom settings of the application: POP3 mail account on the server the distribution is a gecko linux https://geckolinux.github.io/ in particular "gecko linux next plasma". GeckoLinux NEXT editions have a stable openSUSE Leap base, combined with additional OBS repositories to offer the latest version of popular desktop environments like KDE The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x0000000000000000 in ?? () #5 0x00007fb3e81d8e83 in opj_destroy_codec () from /usr/lib64/libopenjp2.so.7 #6 0x00007fb3e891264d in JPXStreamPrivate::init2(CODEC_FORMAT, unsigned char*, int, bool) () from /usr/lib64/libpoppler.so.105 #7 0x00007fb3e8912ad0 in JPXStream::init() () from /usr/lib64/libpoppler.so.105 #8 0x00007fb3e89130f6 in JPXStream::getImageParams(int*, StreamColorSpaceMode*) () from /usr/lib64/libpoppler.so.105 #9 0x00007fb3e881d57f in Gfx::doImage(Object*, Stream*, bool) () from /usr/lib64/libpoppler.so.105 #10 0x00007fb3e8823b6f in Gfx::opXObject(Object*, int) () from /usr/lib64/libpoppler.so.105 #11 0x00007fb3e8818f3f in Gfx::go(bool) () from /usr/lib64/libpoppler.so.105 #12 0x00007fb3e88193cf in Gfx::display(Object*, bool) () from /usr/lib64/libpoppler.so.105 #13 0x00007fb3e8872d23 in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) () from /usr/lib64/libpoppler.so.105 #14 0x00007fb3e8e73994 in ?? () from /usr/lib64/libKPimItinerary.so.5 #15 0x00007fb3e8e73dfc in KItinerary::PdfPage::imageCount() const () from /usr/lib64/libKPimItinerary.so.5 #16 0x00007fb3e8e6291c in ?? () from /usr/lib64/libKPimItinerary.so.5 #17 0x00007fb3e8e917f9 in ?? () from /usr/lib64/libKPimItinerary.so.5 #18 0x00007fb3e8e94311 in ?? () from /usr/lib64/libKPimItinerary.so.5 #19 0x00007fb3e8e94644 in KItinerary::ExtractorEngine::extract() () from /usr/lib64/libKPimItinerary.so.5 #20 0x00007fb3e924aced in ?? () from /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so #21 0x00007fb49722a1d5 in MimeTreeParser::ObjectTreeParser::processType(KMime::Content*, MimeTreeParser::ProcessResult&, QByteArray const&) () from /usr/lib64/libKF5MimeTreeParser.so.5 #22 0x00007fb49722a9ad in MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*, bool) () from /usr/lib64/libKF5MimeTreeParser.so.5 #23 0x00007fb49722f890 in MimeTreeParser::MessagePart::parseInternal(KMime::Content*, bool) () from /usr/lib64/libKF5MimeTreeParser.so.5 #24 0x00007fb49722f9f1 in MimeTreeParser::MimeMessagePart::MimeMessagePart(MimeTreeParser::ObjectTreeParser*, KMime::Content*, bool) () from /usr/lib64/libKF5MimeTreeParser.so.5 #25 0x00007fb3da0bf4fe in ?? () from /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_application_gnupgwks.so #26 0x00007fb49722a1d5 in MimeTreeParser::ObjectTreeParser::processType(KMime::Content*, MimeTreeParser::ProcessResult&, QByteArray const&) () from /usr/lib64/libKF5MimeTreeParser.so.5 #27 0x00007fb49722a9ad in MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*, bool) () from /usr/lib64/libKF5MimeTreeParser.so.5 #28 0x00007fb49722ac9b in MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) () from /usr/lib64/libKF5MimeTreeParser.so.5 #29 0x00007fb4985a2045 in ?? () from /usr/lib64/libKF5MessageViewer.so.5 #30 0x00007fb4985a432a in ?? () from /usr/lib64/libKF5MessageViewer.so.5 #31 0x00007fb4985a49ad in ?? () from /usr/lib64/libKF5MessageViewer.so.5 #32 0x00007fb49b88eb17 in ?? () from /usr/lib64/libQt5Core.so.5 #33 0x00007fb49b8936e7 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5 #34 0x00007fb49b893a48 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5 #35 0x00007fb49b885563 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #36 0x00007fb49c7f637c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #37 0x00007fb49c7fd170 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #38 0x00007fb49b851403 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #39 0x00007fb49b8b3019 in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #40 0x00007fb49b8b37e1 in ?? () from /usr/lib64/libQt5Core.so.5 #41 0x00007fb486eb54a4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #42 0x00007fb486eb5840 in ?? () from /usr/lib64/libglib-2.0.so.0 #43 0x00007fb486eb58cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #44 0x00007fb49b8b3b8c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #45 0x00007fb49b84fc8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #46 0x00007fb49b859487 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #47 0x000055918ef72d93 in ?? () #48 0x00007fb49ae0b34a in __libc_start_main () from /lib64/libc.so.6 #49 0x000055918ef72eba in ?? () [Inferior 1 (process 7760) detached] The reporter indicates this bug may be a duplicate of or related to bug 409001. Possible duplicates by query: bug 416318, bug 409001. Reported using DrKonqi
as in the original report, renaming messageviewer_bodypartformatter_semantic.so prevented the crash, email and pdf were readable. tux:/usr/lib64/qt5/plugins/messageviewer/bodypartformatter # mv ./messageviewer_bodypartformatter_semantic.so ./messageviewer_bodypartformatter_semantic.so.bak
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with KMail 25.12.1.
.