Version: onbekend (using 4.2.00 (KDE 4.2.0) "release 82.2", KDE:KDE4:Factory:Desktop / openSUSE_11.0) Compiler: gcc OS: Linux (i686) release 2.6.25.20-0.1-default I've got a crash in KMail when I selected multiple messages of my INBOX. Selecting the messages one by one didn't cause any problems. Here is the backtrace: Programma: Kontact (kontact), signaal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] Thread 1 (Thread 0xb4baaa60 (LWP 18292)): [KCrash Handler] #6 DwEntity::Headers (this=0xbfacc674) at /usr/src/debug/kdepim-4.2.0/mimelib/entity.cpp:241 #7 0xb12e2505 in KMMessage::from (this=0x946d438) at /usr/src/debug/kdepim-4.2.0/kmail/kmmessage.cpp:1943 #8 0xb153bdc3 in KMail::FancyHeaderStyle::format (this=0x8724d78, message=0x946d438, strategy=0x82fa710, vCardName=@0xbfad2070, printing=false, topLevel=true) at /usr/src/debug/kdepim-4.2.0/kmail/headerstyle.cpp:456 #9 0xb13dc3c3 in KMReaderWin::writeMsgHeader (this=0x869fd20, aMsg=0x946d438, hasVCard=false, topLevel=<value optimized out>) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1733 #10 0xb13e75da in KMReaderWin::parseMsg (this=0x869fd20, aMsg=0x946d438) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1618 #11 0xb13d8848 in KMReaderWin::displayMessage (this=0x869fd20) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555 #12 0xb13d8a60 in KMReaderWin::updateReaderWin (this=0x869fd20) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495 #13 0xb13e6ed0 in KMReaderWin::qt_metacall (this=0x869fd20, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfad2398) at /usr/src/debug/kdepim-4.2.0/build/kmail/kmreaderwin.moc:164 #14 0xb6889740 in QMetaObject::activate (sender=0x869fd70, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031 #15 0xb688a4c2 in QMetaObject::activate (sender=0x869fd70, m=0xb6958904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101 #16 0xb68c4bc7 in QTimer::timeout (this=0x869fd70) at .moc/release-shared/moc_qtimer.cpp:126 #17 0xb68901de in QTimer::timerEvent (this=0x869fd70, e=0xbfad2860) at kernel/qtimer.cpp:257 #18 0xb68841ff in QObject::event (this=0x869fd70, e=0xbfad2860) at kernel/qobject.cpp:1120 #19 0xb5e1982c in QApplicationPrivate::notify_helper (this=0x806d060, receiver=0x869fd70, e=0xbfad2860) at kernel/qapplication.cpp:3803 #20 0xb5e216ce in QApplication::notify (this=0xbfad2b38, receiver=0x869fd70, e=0xbfad2860) at kernel/qapplication.cpp:3393 #21 0xb6ddb68d in KApplication::notify (this=0xbfad2b38, receiver=0x869fd70, event=0xbfad2860) at /usr/src/debug/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307 #22 0xb6874a71 in QCoreApplication::notifyInternal (this=0xbfad2b38, receiver=0x869fd70, event=0xbfad2860) at kernel/qcoreapplication.cpp:587 #23 0xb68a2de6 in QTimerInfoList::activateTimers (this=0x8071594) at kernel/qcoreapplication.h:209 #24 0xb689f2b0 in timerSourceDispatch (source=0x8071560) at kernel/qeventdispatcher_glib.cpp:160 #25 0xb52bb2d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0xb52be85b in ?? () from /usr/lib/libglib-2.0.so.0 #27 0xb52be9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0xb689f208 in QEventDispatcherGlib::processEvents (this=0x806d1a0, flags={i = -1079170552}) at kernel/qeventdispatcher_glib.cpp:319 #29 0xb5eb2885 in QGuiEventDispatcherGlib::processEvents (this=0x806d1a0, flags={i = -1079170504}) at kernel/qguieventdispatcher_glib.cpp:193 #30 0xb687314a in QEventLoop::processEvents (this=0xbfad2ab0, flags={i = -1079170440}) at kernel/qeventloop.cpp:143 #31 0xb687330a in QEventLoop::exec (this=0xbfad2ab0, flags={i = -1079170376}) at kernel/qeventloop.cpp:194 #32 0xb68759a5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #33 0xb5e196a7 in QApplication::exec () at kernel/qapplication.cpp:3331 #34 0x0804bf8f in main (argc=1, argv=0xbfad2e34) at /usr/src/debug/kdepim-4.2.0/kontact/src/main.cpp:218
This may be related to bug 181443
The backtrace is the same as the one at comment #7, closing as duplicate. *** This bug has been marked as a duplicate of bug 181443 ***