Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.3.0-8.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: I clicked on a message that was encrypted with GnuPG (simple inline mode, no MIME) -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f5642502840 (LWP 3815))] Thread 4 (Thread 0x7f56366a5700 (LWP 3872)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x000000352d1b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x352db7cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x000000352d1b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x0000003254c07d90 in start_thread (arg=0x7f56366a5700) at pthread_create.c:309 #4 0x00000032540f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f5635da4700 (LWP 3873)): #0 0x00000032540e85c3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0000003158c45448 in g_main_context_poll (n_fds=1, fds=0x7f56300013e0, priority=<optimized out>, timeout=2337, context=0x7f56300009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f56300009a0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3084 #3 0x0000003158c4590c in g_main_context_iteration (context=0x7f56300009a0, may_block=1) at gmain.c:3152 #4 0x000000351e5a8626 in QEventDispatcherGlib::processEvents (this=0x7f56300008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #5 0x000000351e578a12 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x000000351e578c67 in QEventLoop::exec (this=0x7f5635da3d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x000000351e478ad7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #8 0x000000351e47bb1b in QThreadPrivate::start (arg=0x114e3f0) at thread/qthread_unix.cpp:298 #9 0x0000003254c07d90 in start_thread (arg=0x7f5635da4700) at pthread_create.c:309 #10 0x00000032540f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f55ef835700 (LWP 4788)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x000000351e47bf8f in wait (time=30000, this=0x17af550) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=<optimized out>, mutex=0x17af4f8, time=30000) at thread/qwaitcondition_unix.cpp:158 #3 0x000000351e46f55f in QThreadPoolThread::run (this=0x17b07e0) at concurrent/qthreadpool.cpp:141 #4 0x000000351e47bb1b in QThreadPrivate::start (arg=0x17b07e0) at thread/qthread_unix.cpp:298 #5 0x0000003254c07d90 in start_thread (arg=0x7f55ef835700) at pthread_create.c:309 #6 0x00000032540f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f5642502840 (LWP 3815)): [KCrash Handler] #6 0x000000352e443eb4 in KMime::Content::parent() const () from /usr/lib64/libkmime.so.4 #7 0x000000359de354e5 in MessageCore::NodeHelper::nextSibling (node=0x43e63ec0) at /usr/src/debug/kdepim-4.8.2/messagecore/nodehelper.cpp:32 #8 0x000000359e6862d9 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff8d82f070, node=0x43e63ec0) at /usr/src/debug/kdepim-4.8.2/messageviewer/objecttreeparser.cpp:296 #9 0x000000359e6b796f in MessageViewer::ViewerPrivate::parseContent (this=0x1136e50, content=0x43e63ec0) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:866 #10 0x000000359e6ba3fa in MessageViewer::ViewerPrivate::displayMessage (this=0x1136e50) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:738 #11 0x000000359e6baca2 in MessageViewer::ViewerPrivate::updateReaderWin (this=0x1136e50) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:2018 #12 0x000000359e6be1fa in MessageViewer::ViewerPrivate::qt_static_metacall (_o=0x1136e50, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdepim-4.8.2/x86_64-redhat-linux-gnu/messageviewer/viewer_p.moc:205 #13 0x000000351e58d571 in QMetaObject::activate (sender=0x1136ed8, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #14 0x000000351e5924d9 in QObject::event (this=0x1136ed8, e=<optimized out>) at kernel/qobject.cpp:1157 #15 0x000000351ebc9bc4 in notify_helper (e=0x7fff8d82fca0, receiver=0x1136ed8, this=0x9fd010) at kernel/qapplication.cpp:4554 #16 QApplicationPrivate::notify_helper (this=0x9fd010, receiver=0x1136ed8, e=0x7fff8d82fca0) at kernel/qapplication.cpp:4526 #17 0x000000351ebcea43 in QApplication::notify (this=0x7fff8d830050, receiver=0x1136ed8, e=0x7fff8d82fca0) at kernel/qapplication.cpp:4415 #18 0x0000003522851f96 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #19 0x000000351e5798dc in QCoreApplication::notifyInternal (this=0x7fff8d830050, receiver=0x1136ed8, event=0x7fff8d82fca0) at kernel/qcoreapplication.cpp:876 #20 0x000000351e5aa392 in sendEvent (event=0x7fff8d82fca0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #21 QTimerInfoList::activateTimers (this=0x9ff950) at kernel/qeventdispatcher_unix.cpp:611 #22 0x000000351e5a7d9d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #23 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #24 0x0000003158c44f3d in g_main_dispatch (context=0x9ffe10) at gmain.c:2441 #25 g_main_context_dispatch (context=0x9ffe10) at gmain.c:3011 #26 0x0000003158c45738 in g_main_context_iterate (context=0x9ffe10, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3089 #27 0x0000003158c4590c in g_main_context_iteration (context=0x9ffe10, may_block=1) at gmain.c:3152 #28 0x000000351e5a85bf in QEventDispatcherGlib::processEvents (this=0x97eaf0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #29 0x000000351ec6c8ce in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #30 0x000000351e578a12 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #31 0x000000351e578c67 in QEventLoop::exec (this=0x7fff8d82ff30, flags=...) at kernel/qeventloop.cpp:204 #32 0x000000351e57d665 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #33 0x0000000000402d23 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdepim-4.8.2/kmail/main.cpp:145 This bug may be a duplicate of or related to bug 279749. Possible duplicates by query: bug 292040, bug 286024. Reported using DrKonqi
Created attachment 70648 [details] New crash information added by DrKonqi kmail (4.9 pre) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1 - What I was doing when the application crashed: Clicked on an encrypted message. Dialog opened up asking for my password, when I entered it, kmail crashed. -- Backtrace (Reduced): #6 0x00007f1f1225c4f4 in KMime::Content::parent (this=0x8804470) at /home/emilsedgh/kde/sc/kdepimlibs/kmime/kmime_content.cpp:949 #7 0x00007f1f0b873a45 in MessageCore::NodeHelper::nextSibling (node=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messagecore/nodehelper.cpp:32 #8 0x00007f1f08b677c7 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff00971740, node=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messageviewer/objecttreeparser.cpp:296 #9 0x00007f1f08b9bcaf in MessageViewer::ViewerPrivate::parseContent (this=0x1f59640, content=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messageviewer/viewer_p.cpp:952 #10 0x00007f1f08b9e434 in MessageViewer::ViewerPrivate::displayMessage (this=0x1f59640) at /home/emilsedgh/kde/sc/kdepim/messageviewer/viewer_p.cpp:824
Ok I need to configure kmail to open a dialogbox to decrypt it.... Don't know how to do it... Perhaps you have some infos about it. Yes for the moment I didn't test crypto + kmail.
Hi Laurent. Should I describe a KMail feature to KMail's maintainer? :p Well, I've setup gpg keys using KGPG/Kleopatra. Then someone sent me an encrypted message. I think you can even setup a gpg key and then send an encrypted email to yourself.
"Should I describe a KMail feature to KMail's maintainer? :p" yes :) Thanks will look at it soon. I never really test crypto feature so it's the time to test/debug it :)
Laurent you probably don't have gpg-agent running, then KMail behaves a bit ugly and does not open a dialogbox to decrypt it. Start it on the command line: eval $(gpg-agent --daemon) before starting Kontact. This should be autostarted by your distribution. I've just tested with an inline openpgp (Content-Type text/Plain, Content-Disposition iniline) mail sent by kontact and could not reproduce this. (Found another bug though that the mail is decrypted without explicitly clicking on decrypt -> privacy leak) :( Could someone please send me a message that whould crash for him to aheinecke@intevation.de My Key fingerprint = B248 32EB D9AA DA17 15D2 A2E5 5DE9 385C C978 22F5
Created attachment 70873 [details] New crash information added by DrKonqi kmail (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Just clicked on the mail. KMail crashes (does not depent on entering the correct passphrase) -- Backtrace (Reduced): #6 0x0000003c1ea43eb4 in KMime::Content::parent() const () from /usr/lib64/libkmime.so.4 #7 0x0000003c226354e5 in MessageCore::NodeHelper::nextSibling (node=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messagecore/nodehelper.cpp:32 #8 0x0000003c22e862d9 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff62397270, node=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messageviewer/objecttreeparser.cpp:296 #9 0x0000003c22eb796f in MessageViewer::ViewerPrivate::parseContent (this=0x1b1c960, content=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:866 #10 0x0000003c22eba3fa in MessageViewer::ViewerPrivate::displayMessage (this=0x1b1c960) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:738
Created attachment 74260 [details] New crash information added by DrKonqi kmail (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.3 - What I was doing when the application crashed: Clicked on an encrypted message. Dialog opened up asking for my password, when I entered it, kmail crashed. -- Backtrace (Reduced): #5 0x0000003b55c43ee4 in KMime::Content::parent() const () from /lib64/libkmime.so.4 #6 0x0000003b62e2c386 in MessageCore::NodeHelper::nextSibling(KMime::Content const*) () from /lib64/libmessagecore.so.4 #7 0x0000003b63e8cdd4 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*) () from /lib64/libmessageviewer.so.4 #8 0x0000003b63ec21b0 in MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from /lib64/libmessageviewer.so.4 #9 0x0000003b63ec3a7c in MessageViewer::ViewerPrivate::displayMessage() () from /lib64/libmessageviewer.so.4
Created attachment 75603 [details] New crash information added by DrKonqi kmail (4.9.3) on KDE Platform 4.9.3 using Qt 4.8.4 - What I was doing when the application crashed: tried to decrypt a non-mime GnuPG message -----BEGIN PGP MESSAGE----- Charset: ISO-8859-1 Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org hQQOAzdCI0LImZTFEA/+PP6cGT7gDgBI19R12D1rGA/Md1xvRkBfumttAz7gN1l1 qz3pqeT3qfQkKhDd4co6ldIt68zpjnN4282rltzy73VQF/Hn7/i6/0FV7h2Z65DP 4QeSE2i3pDfk5nEGKzvUUlwo6JgYkbt92tCG5TTnJDy92xF5B+1udgKa5/a5Raqg 6Cw3zrjqOU+mS2sK+5hTJ+yoXsA4wvnGHIZ7MN7KQyV5kYINsN66L+2rasu53+1S LAV7oyaLoxD20Eih9dlMsfCClbJ0XN90x4wBTtPcYpyu6RZEUvbmKV0VaGQdU1gM YkMYWHtH4OLp9W/pHVE72WJ8zzSY++u4VtKltfkfZx/ElVlEyUBoMYTc6x8uoXV7 DBl4TCDfmRuVNNN4TTEkb2bM02rVQYVey5i4Z79CQtCrSPiJ/H/UX+bmCYJ7f55q […] -- Backtrace (Reduced): #6 0x000000394c443e84 in KMime::Content::parent (this=0x36b1180) at /usr/src/debug/kdepimlibs-4.9.3/kmime/kmime_content.cpp:949 #7 0x000000351562c336 in MessageCore::NodeHelper::nextSibling (node=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messagecore/nodehelper.cpp:32 #8 0x00007ffa2d307cc4 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff0cd19e90, node=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messageviewer/objecttreeparser.cpp:296 #9 0x00007ffa2d33d530 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x2714f00, content=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messageviewer/viewer_p.cpp:1023 #10 0x00007ffa2d33edfc in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x2714f00) at /usr/src/debug/kdepim-4.9.3/messageviewer/viewer_p.cpp:895
Created attachment 77821 [details] New crash information added by DrKonqi kmail (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: Klicking on a non-MIME-encrypted PGP mail… -- Backtrace (Reduced): #6 0x000000367d043e44 in KMime::Content::parent (this=0x4f9c9d0) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_content.cpp:952 #7 0x000000368302c106 in MessageCore::NodeHelper::nextSibling (node=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messagecore/nodehelper.cpp:32 #8 0x0000003683890224 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff66518100, node=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messageviewer/objecttreeparser.cpp:296 #9 0x00000036838c4f20 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x2bd4210, content=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messageviewer/viewer_p.cpp:974 #10 0x00000036838c674c in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x2bd4210) at /usr/src/debug/kdepim-4.10.1/messageviewer/viewer_p.cpp:846
Can someone attach such a mail that let kmail crash? I'm actually working in the crypto part of kmail, and test all different crypto types and had never this problem with a chrashing kmail. This would make the life easier for me to find the bug.
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!
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!