Bug 323696 - Kmail crashes when trying to display a PGP encrypted message
Summary: Kmail crashes when trying to display a PGP encrypted message
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.5
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-08-19 00:27 UTC by Guido Winkelmann
Modified: 2018-10-27 04:18 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.55 KB, text/plain)
2013-08-20 08:25 UTC, Marius Herzog
Details
New crash information added by DrKonqi (7.81 KB, text/plain)
2013-09-08 10:44 UTC, micu
Details
New crash information added by DrKonqi (6.64 KB, text/plain)
2013-10-08 20:31 UTC, Eric L
Details
New crash information added by DrKonqi (8.03 KB, text/plain)
2013-10-18 12:17 UTC, sean_mccully
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guido Winkelmann 2013-08-19 00:27:10 UTC
After clicking on a PGP encrypted message (encrypted to me) in the message list, and subsequently entering my PGP key's passphrase, KMail crashed.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Click on a PGP encrypted message, encrypted to the user, in the message list
2. In the dialog that pops up, enter the key's passphrase
3. Press Enter
Actual Results:  
KMail crashes with a segmentation fault

Expected Results:  
KMail should display the decrypted contents of the message.

Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f52b992a780 (LWP 3645))]

Thread 3 (Thread 0x7f529a2d7700 (LWP 3672)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f52aa29ce14 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f52aac8f1e0 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:2495
#2  0x00007f52aa29cf49 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1618
#3  0x00007f52b4979006 in start_thread (arg=0x7f529a2d7700) at pthread_create.c:305
#4  0x00007f52b6bc254d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f52999d6700 (LWP 3676)):
#0  g_mutex_get_impl (mutex=0x7f52940009a0) at gthread-posix.c:118
#1  0x00007f52aebfbb09 in g_mutex_unlock (mutex=<optimized out>) at gthread-posix.c:227
#2  0x00007f52aebc0fda in g_main_context_query (context=0x7f52940009a0, max_priority=2147483647, timeout=0x7f52999d5ccc, fds=<optimized out>, n_fds=1) at gmain.c:2941
#3  0x00007f52aebc162a in g_main_context_iterate (dispatch=1, block=1, context=0x7f52940009a0, self=<optimized out>) at gmain.c:3128
#4  g_main_context_iterate (context=0x7f52940009a0, block=1, dispatch=1, self=<optimized out>) at gmain.c:3083
#5  0x00007f52aebc17cc in g_main_context_iteration (context=0x7f52940009a0, may_block=1) at gmain.c:3207
#6  0x00007f52b755938e in QEventDispatcherGlib::processEvents (this=0x7f52940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x00007f52b7528f12 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f52b7529197 in QEventLoop::exec (this=0x7f52999d5de0, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f52b7427f5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#10 0x00007f52b742a77c in QThreadPrivate::start (arg=0x83f620) at thread/qthread_unix.cpp:338
#11 0x00007f52b4979006 in start_thread (arg=0x7f52999d6700) at pthread_create.c:305
#12 0x00007f52b6bc254d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f52b992a780 (LWP 3645)):
[KCrash Handler]
#6  0x00007f52b34ae6a4 in KMime::Content::parent (this=0xf74100) at /var/tmp/portage/kde-base/kdepimlibs-4.10.5/work/kdepimlibs-4.10.5/kmime/kmime_content.cpp:952
#7  0x00007f52b2b80a75 in MessageCore::NodeHelper::nextSibling (node=0xf74100) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messagecore/nodehelper.cpp:32
#8  0x00007f52afa552e0 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff093f3ba0, node=0xf74100) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/objecttreeparser.cpp:296
#9  0x00007f52afa8af0f in MessageViewer::ViewerPrivate::parseContent (this=0xa0ddd0, content=0xf74100) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/viewer_p.cpp:974
#10 0x00007f52afa8d2b6 in MessageViewer::ViewerPrivate::displayMessage (this=0xa0ddd0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/viewer_p.cpp:846
#11 0x00007f52afa8daf1 in MessageViewer::ViewerPrivate::updateReaderWin (this=0xa0ddd0) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/viewer_p.cpp:2185
#12 0x00007f52afa90d1a in MessageViewer::ViewerPrivate::qt_static_metacall (_o=0xa0ddd0, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5_build/messageviewer/viewer_p.moc:234
#13 0x00007f52b753e1b1 in QMetaObject::activate (sender=0xa0de60, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539
#14 0x00007f52b7543979 in QObject::event (this=0xa0de60, e=<optimized out>) at kernel/qobject.cpp:1156
#15 0x00007f52b7a6b0b4 in notify_helper (e=0x7fff093f4840, receiver=0xa0de60, this=0x6724c0) at kernel/qapplication.cpp:4562
#16 QApplicationPrivate::notify_helper (this=0x6724c0, receiver=0xa0de60, e=0x7fff093f4840) at kernel/qapplication.cpp:4534
#17 0x00007f52b7a6fd61 in QApplication::notify (this=0x7fff093f4be0, receiver=0xa0de60, e=0x7fff093f4840) at kernel/qapplication.cpp:3944
#18 0x00007f52b932ce88 in KApplication::notify (this=0x7fff093f4be0, receiver=0xa0de60, event=0x7fff093f4840) at /var/tmp/portage/kde-base/kdelibs-4.10.5-r1/work/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#19 0x00007f52b752a44b in QCoreApplication::notifyInternal (this=0x7fff093f4be0, receiver=0xa0de60, event=0x7fff093f4840) at kernel/qcoreapplication.cpp:946
#20 0x00007f52b755bdaa in sendEvent (event=0x7fff093f4840, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#21 QTimerInfoList::activateTimers (this=0x672440) at kernel/qeventdispatcher_unix.cpp:621
#22 0x00007f52b7558bbd in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#23 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#24 0x00007f52aebc13d2 in g_main_dispatch (context=0x673a00) at gmain.c:2539
#25 g_main_context_dispatch (context=0x673a00) at gmain.c:3075
#26 0x00007f52aebc1710 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x673a00, self=<optimized out>) at gmain.c:3146
#27 g_main_context_iterate (context=0x673a00, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3083
#28 0x00007f52aebc17cc in g_main_context_iteration (context=0x673a00, may_block=1) at gmain.c:3207
#29 0x00007f52b7559336 in QEventDispatcherGlib::processEvents (this=0x660120, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x00007f52b7b0ec86 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007f52b7528f12 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007f52b7529197 in QEventLoop::exec (this=0x7fff093f4aa0, flags=...) at kernel/qeventloop.cpp:204
#33 0x00007f52b752e4c7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#34 0x00000000004030f7 in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.10.5/work/kmail-4.10.5/kmail/main.cpp:146
Comment 1 Marius Herzog 2013-08-20 08:25:09 UTC
Created attachment 81799 [details]
New crash information added by DrKonqi

kmail (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.4

- What I was doing when the application crashed:

- open a pgp-encrypted e-mail
- enter password
- kmail crashes

kmail does not always crash, roughly 3 out of 4 times.

-- Backtrace (Reduced):
#6  0x00007f5861769964 in KMime::Content::parent (this=0x252a290) at /var/tmp/portage/kde-base/kdepimlibs-4.10.5/work/kdepimlibs-4.10.5/kmime/kmime_content.cpp:952
#7  0x00007f5860e65306 in MessageCore::NodeHelper::nextSibling (node=0x252a290) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messagecore/nodehelper.cpp:32
#8  0x00007f585dde7046 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff911f6730, node=0x252a290) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/objecttreeparser.cpp:296
#9  0x00007f585de1ac50 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x1e32130, content=0x252a290) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/viewer_p.cpp:974
#10 0x00007f585de1c3ec in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x1e32130) at /var/tmp/portage/kde-base/kdepim-common-libs-4.10.5/work/kdepim-common-libs-4.10.5/messageviewer/viewer_p.cpp:846
Comment 2 Guido Winkelmann 2013-08-22 22:10:38 UTC
More information:

Kmail crashes particularly often when entering a wrong passphrase for decryption or when pressing cancel on the passphrase dialog.

If Kmail has managed to successfully show the mail in question at least once, either decrypted or encrypted, it will usually not crash again when showing the same message, until restarted.
Comment 3 micu 2013-09-08 10:44:39 UTC
Created attachment 82217 [details]
New crash information added by DrKonqi

kmail (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.5

- What I was doing when the application crashed:

Klicked on a inline-PGP encrypted message, entered my password, klicked OK → boom

-- Backtrace (Reduced):
#6  0x0000003280a43184 in KMime::Content::parent (this=this@entry=0x6b49140) at /usr/src/debug/kdepimlibs-4.11.1/kmime/kmime_content.cpp:953
#7  0x0000003286e3aa27 in MessageCore::NodeHelper::nextSibling (node=node@entry=0x6b49140) at /usr/src/debug/kdepim-4.11.1/messagecore/helpers/nodehelper.cpp:32
#8  0x0000003287ea30ef in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fff0125dbe0, node=node@entry=0x6b49140) at /usr/src/debug/kdepim-4.11.1/messageviewer/viewer/objecttreeparser.cpp:296
#9  0x0000003287ea4bd9 in MessageViewer::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fff0125dbe0, node=node@entry=0x6b49140) at /usr/src/debug/kdepim-4.11.1/messageviewer/viewer/objecttreeparser.cpp:266
#10 0x0000003287ed0e28 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x20a5200, content=0x6b49140) at /usr/src/debug/kdepim-4.11.1/messageviewer/viewer/viewer_p.cpp:1007
Comment 4 Sandro Knauß 2013-09-30 00:17:16 UTC
(In reply to comment #2)
> More information:
> 
> Kmail crashes particularly often when entering a wrong passphrase for
> decryption or when pressing cancel on the passphrase dialog.
> 
> If Kmail has managed to successfully show the mail in question at least
> once, either decrypted or encrypted, it will usually not crash again when
> showing the same message, until restarted.

Hitting the cancel button sounds like #325197
Comment 5 Sandro Knauß 2013-09-30 00:20:55 UTC
Sorry I mean #323916
Comment 6 Eric L 2013-10-08 20:31:07 UTC
Created attachment 82727 [details]
New crash information added by DrKonqi

kmail (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.5

- What I was doing when the application crashed:

Trying to open a pgp encrypted mail message.

I clicked on the email, typed in the password, and had a segment fault.

-- Backtrace (Reduced):
#5  0x00000033e9643184 in KMime::Content::parent() const () from /lib64/libkmime.so.4
#6  0x000000340883aa27 in MessageCore::NodeHelper::nextSibling(KMime::Content const*) () from /lib64/libmessagecore.so.4
#7  0x0000003d068a30ef in MessageViewer::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*) () from /lib64/libmessageviewer.so.4
#8  0x0000003d068d0e28 in MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from /lib64/libmessageviewer.so.4
#9  0x0000003d068d15d2 in MessageViewer::ViewerPrivate::displayMessage() () from /lib64/libmessageviewer.so.4
Comment 7 sean_mccully 2013-10-18 12:17:20 UTC
Created attachment 82922 [details]
New crash information added by DrKonqi

kmail (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5

- What I was doing when the application crashed:
Trying to display PGP Encrypted Message, after entering Passphrase KMail crashed. This does not happen everytime.

-- Backtrace (Reduced):
#6  0x0000003280e44174 in KMime::Content::parent (this=this@entry=0x4f3b2d0) at /usr/src/debug/kdepimlibs-4.11.2/kmime/kmime_content.cpp:953
#7  0x000000328a83b4d7 in MessageCore::NodeHelper::nextSibling (node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messagecore/helpers/nodehelper.cpp:32
#8  0x00000032898a5e47 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=this@entry=0x7fff58f2a1b0, node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/objecttreeparser.cpp:296
#9  0x00000032898a79c9 in MessageViewer::ObjectTreeParser::parseObjectTree (this=this@entry=0x7fff58f2a1b0, node=node@entry=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/objecttreeparser.cpp:266
#10 0x00000032898d5b9b in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0xedc5c0, content=0x4f3b2d0) at /usr/src/debug/kdepim-4.11.2/messageviewer/viewer/viewer_p.cpp:1007
Comment 8 Sandro Knauß 2013-10-19 12:19:00 UTC
* Is it an Inline PGP message or not?
* is gpg-agent running?
Comment 9 Guido Winkelmann 2013-11-08 00:08:04 UTC
(In reply to comment #8)
> * Is it an Inline PGP message or not?

At least one of the messages that causes the crash was inline.

> * is gpg-agent running?

No.
Comment 10 Marius Herzog 2014-03-10 14:07:47 UTC
(In reply to comment #8)
> * Is it an Inline PGP message or not?

No

> * is gpg-agent running?

No, but starting gpg-agent does not affect crash behaviour
Comment 11 Andrew Crouthamel 2018-09-25 03:33:16 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 set the bug status 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 12 Andrew Crouthamel 2018-10-27 04:18:57 UTC
Dear Bug Submitter,

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!