Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.30-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: In kmail I had expired many messages, which moved them to another folder. This was being synchronised (dimap). During the process I clicked on a new message to view it, and the crash occurred. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KMimeType::d_func (this=0x0, url=...) at ../../kdecore/services/kmimetype.h:48 #6 KMimeType::iconName (this=0x0, url=...) at ../../kdecore/services/kmimetype.cpp:681 #7 0x00007f5407bc3388 in KMail::ObjectTreeParser::processApplicationMsTnefSubtype (this=0x7fff2109e410, node=<value optimized out>, result=<value optimized out>) at ../../kmail/objecttreeparser.cpp:1900 #8 0x00007f5407bce6be in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff2109e410, node=0x2b748cb0) at ../../kmail/objecttreeparser.cpp:296 #9 0x00007f5407bce8b5 in KMail::ObjectTreeParser::stdChildHandling (this=0x7fff2109e720, child=0x121534700) at ../../kmail/objecttreeparser.cpp:1146 #10 0x00007f5407bcec34 in KMail::ObjectTreeParser::processMultiPartMixedSubtype (this=0x7fff2109dfb0, node=<value optimized out>) at ../../kmail/objecttreeparser.cpp:1159 #11 0x00007f5407bce6be in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff2109e720, node=0x313ff70) at ../../kmail/objecttreeparser.cpp:296 #12 0x00007f5407a53b69 in KMReaderWin::parseMsg (this=0x2d77d60, aMsg=0x5029550) at ../../kmail/kmreaderwin.cpp:1682 #13 0x00007f5407a42ada in KMReaderWin::displayMessage (this=0x2d77d60) at ../../kmail/kmreaderwin.cpp:1608 #14 0x00007f5407a42cb4 in KMReaderWin::updateReaderWin (this=0x2d77d60) at ../../kmail/kmreaderwin.cpp:1548 #15 0x00007f5407a4fd9d in KMReaderWin::qt_metacall (this=0x2d77d60, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff2109edc0) at ./kmreaderwin.moc:168 #16 0x00007f541dd57df2 in QMetaObject::activate (sender=0x2d77e08, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xff0f9d01) at kernel/qobject.cpp:3112 #17 0x00007f541dd52353 in QObject::event (this=0x2d77e08, e=0x0) at kernel/qobject.cpp:1074 #18 0x00007f541d1bc01d in QApplicationPrivate::notify_helper (this=0x1e57fc0, receiver=0x2d77e08, e=0x7fff2109f470) at kernel/qapplication.cpp:4065 #19 0x00007f541d1c407a in QApplication::notify (this=0x7fff2109f7e0, receiver=0x2d77e08, e=0x7fff2109f470) at kernel/qapplication.cpp:4030 #20 0x00007f541e6e8e06 in KApplication::notify (this=0x7fff2109f7e0, receiver=0x2d77e08, event=0x7fff2109f470) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x00007f541dd42c9c in QCoreApplication::notifyInternal (this=0x7fff2109f7e0, receiver=0x2d77e08, event=0x7fff2109f470) at kernel/qcoreapplication.cpp:610 #22 0x00007f541dd6f2c6 in QCoreApplication::sendEvent (this=0x1e5b8c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #23 QTimerInfoList::activateTimers (this=0x1e5b8c0) at kernel/qeventdispatcher_unix.cpp:580 #24 0x00007f541dd6b658 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184 #25 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231 #26 0x00007f5416a4d13a in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #27 0x00007f5416a50998 in ?? () from /lib/libglib-2.0.so.0 #28 0x00007f5416a50b4c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #29 0x00007f541dd6b39c in QEventDispatcherGlib::processEvents (this=0x1e2ef70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #30 0x00007f541d252f1f in QGuiEventDispatcherGlib::processEvents (this=0x7fff2109dfb0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #31 0x00007f541dd41562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #32 0x00007f541dd41934 in QEventLoop::exec (this=0x7fff2109f720, flags=...) at kernel/qeventloop.cpp:201 #33 0x00007f541dd43ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0x0000000000403f17 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218 Reported using DrKonqi
Having restarted kontact, it seems that the crash is simply triggered by trying to read the email in question (nothing to do with the move/synchronisation on-going at the time). I forwarded the offending email from another program and again it crashed kmail whenever I clicked on it in the message list. Unfortunately I no longer have a copy of the email, as I needed to delete it (using another program). I will post another example if the problem recurs.
Hi again, I can confirm this on another (similar) computer with the same email - I found another copy. I'm not very keen to post the email, as it contains something confidential. I was hoping to create a reduced test case. I extracted the email from the mbox and was hoping to open it using "kmail --view file://emailname", but I must have misunderstood something as I get an error message "The file or folder smb://emailname/ does not exist." (I can't understand why the smb protocol is used.) If there is any other information that would be helpful, let me know. Regards, Boris
*** This bug has been marked as a duplicate of bug 181351 ***