Bug 409875 - KMail crashes on mail with Itinerary content
Summary: KMail crashes on mail with Itinerary content
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: Git (master)
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-16 21:20 UTC by Nicolas Fella
Modified: 2022-10-23 05:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace (24.53 KB, text/plain)
2019-07-16 21:20 UTC, Nicolas Fella
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Fella 2019-07-16 21:20:00 UTC
Created attachment 121564 [details]
Backtrace

SUMMARY

STEPS TO REPRODUCE
1. Open email with extracted booking information 
2. Move cursor above extracted information

OBSERVED RESULT
KMail crashes

SOFTWARE/OS VERSIONS
KDE Plasma Version: master
KDE Frameworks Version: master
Qt Version: 5.13.0

ADDITIONAL INFORMATION
Wayland session
Happens for all DB emails I tested. Didn't happen with Ryanair
Comment 1 Nicolas Fella 2019-07-16 21:25:54 UTC
Update: It happens on both Wayland and X11, but not on KMail 5.11.2, only master
Comment 2 Christoph Feck 2019-08-05 19:57:59 UTC
Relevant part of backtrace:

Thread 1 (Thread 0x7fb9a01cbb40 (LWP 1802)):
#0  0x00007fb9b6f8a755 in raise () from /usr/lib/libc.so.6
#1  0x00007fb9b8eeaba5 in KCrash::defaultCrashHandler (sig=11) at /home/nico/kde/src/kcrash/src/kcrash.cpp:439
#2  <signal handler called>
#3  0x00007fb9b744cef8 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/libstdc++.so.6
#4  0x00007fb9b64a8203 in MessageViewer::BodyPartURLHandlerManager::statusBarMessage (this=0x557b60866460, url=..., w=0x557b52379a00) at /home/nico/kde/src/messagelib/messageviewer/src/vie--Type <RET> for more, q to quit, c to continue without paging--
wer/urlhandlermanager.cpp:235
#5  0x00007fb9b64a8d5c in MessageViewer::URLHandlerManager::statusBarMessage (this=0x557b5e80fe10, url=..., w=0x557b52379a00) at /home/nico/kde/src/messagelib/messageviewer/src/viewer/urlhandlermanager.cpp:368
#6  0x00007fb9b64905a4 in MessageViewer::ViewerPrivate::slotUrlOn (this=0x557b52379a00, link=...) at /home/nico/kde/src/messagelib/messageviewer/src/viewer/viewer_p.cpp:2087
#7  0x00007fb9b64a5682 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QString const&>, void, void (MessageViewer::ViewerPrivate::*)(QString const&)>::call (f=(void (MessageViewer::ViewerPrivate::*)(MessageViewer::ViewerPrivate * const, const QString &)) 0x7fb9b649038c <MessageViewer::ViewerPrivate::slotUrlOn(QString const&)>, o=0x557b52379a00, arg=0x7ffd2820eb80) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#8  0x00007fb9b64a4450 in QtPrivate::FunctionPointer<void (MessageViewer::ViewerPrivate::*)(QString const&)>::call<QtPrivate::List<QString const&>, void> (f=(void (MessageViewer::ViewerPrivate::*)(MessageViewer::ViewerPrivate * const, const QString &)) 0x7fb9b649038c <MessageViewer::ViewerPrivate::slotUrlOn(QString const&)>, o=0x557b52379a00, arg=0x7ffd2820eb80) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185
#9  0x00007fb9b64a1f6f in QtPrivate::QSlotObject<void (MessageViewer::ViewerPrivate::*)(QString const&), QtPrivate::List<QString const&>, void>::impl (which=1, this_=0x557b5261d150, r=0x557b52379a00, a=0x7ffd2820eb80, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:414
#10 0x00007fb9b7716b70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#11 0x00007fb9b4cafff6 in QWebEnginePage::linkHovered(QString const&) () from /usr/lib/libQt5WebEngineWidgets.so.5
#12 0x00007fb9b4cb12d5 in ?? () from /usr/lib/libQt5WebEngineWidgets.so.5
#13 0x00007fb9adb494c7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
Comment 3 Justin Zobel 2022-09-23 02:22:48 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-10-08 04:53:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-10-23 05:01:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!