Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.28-12-netbook-eeepc i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I regurarly get encrypted email and I use dimap. So I don't want to store them unencrypted. So it happens that new email arrive and currently the last encrypted one is selected. I am then asked to supply the password or cancel. If I cancel then I have to confirm that choice. After doing so kmail / kdepim often crashes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb0af3730 in DwHeaders::FindField (this=0x0, aFieldName=0x8e8e918 "Message-Id") at /build/buildd/kdepim-4.3.2/mimelib/headers.cpp:287 #7 0xb0f5fac0 in KMMessage::headerField (this=0x9395ac0, aName=@0xbfd84934, encodingMode=KMMessage::MessageCharsetEncoding) at /build/buildd/kdepim-4.3.2/kmail/kmmessage.cpp:1990 #8 0xb0f63b47 in KMMessage::msgId (this=0x9395ac0) at /build/buildd/kdepim-4.3.2/kmail/kmmessage.cpp:1888 #9 0xb10750ef in KMReaderWin::parseMsg (this=0x870fa38, aMsg=0x9395ac0) at /build/buildd/kdepim-4.3.2/kmail/kmreaderwin.cpp:1758 #10 0xb1062c8b in KMReaderWin::displayMessage (this=0x870fa38) at /build/buildd/kdepim-4.3.2/kmail/kmreaderwin.cpp:1605 #11 0xb1062ea0 in KMReaderWin::updateReaderWin (this=0x870fa38) at /build/buildd/kdepim-4.3.2/kmail/kmreaderwin.cpp:1545 #12 0xb106fd58 in KMReaderWin::qt_metacall (this=0x870fa38, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd84d68) at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/kmreaderwin.moc:168 #13 0xb5bf31b8 in QMetaObject::activate (sender=0x870fa90, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #14 0xb5bf3e42 in QMetaObject::activate (sender=0x870fa90, m=0xb5cd0904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #15 0xb5c2f687 in QTimer::timeout (this=0x870fa90) at .moc/release-shared/moc_qtimer.cpp:128 #16 0xb5bf95ce in QTimer::timerEvent (this=0x870fa90, e=0xbfd851ec) at kernel/qtimer.cpp:261 #17 0xb5bee16f in QObject::event (this=0x870fa90, e=0xbfd851ec) at kernel/qobject.cpp:1075 #18 0xb60a1d3c in QApplicationPrivate::notify_helper (this=0x819ed98, receiver=0x870fa90, e=0xbfd851ec) at kernel/qapplication.cpp:4056 #19 0xb60aa03e in QApplication::notify (this=0xbfd85498, receiver=0x870fa90, e=0xbfd851ec) at kernel/qapplication.cpp:3603 #20 0xb6c9b49d in KApplication::notify (this=0xbfd85498, receiver=0x870fa90, event=0xbfd851ec) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302 #21 0xb5bddbcb in QCoreApplication::notifyInternal (this=0xbfd85498, receiver=0x870fa90, event=0xbfd851ec) at kernel/qcoreapplication.cpp:610 #22 0xb5c0cd51 in QTimerInfoList::activateTimers (this=0x81a167c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #23 0xb5c093a0 in timerSourceDispatch (source=0x81a1648) at kernel/qeventdispatcher_glib.cpp:165 #24 0xb4caeb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb4cb20eb in ?? () from /usr/lib/libglib-2.0.so.0 #26 0xb4cb2268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb5c092f8 in QEventDispatcherGlib::processEvents (this=0x817f028, flags={i = -1076341912}) at kernel/qeventdispatcher_glib.cpp:327 #28 0xb6143a75 in QGuiEventDispatcherGlib::processEvents (this=0x817f028, flags={i = -1076341864}) at kernel/qguieventdispatcher_glib.cpp:202 #29 0xb5bdc1fa in QEventLoop::processEvents (this=0xbfd85410, flags={i = -1076341800}) at kernel/qeventloop.cpp:149 #30 0xb5bdc642 in QEventLoop::exec (this=0xbfd85410, flags={i = -1076341736}) at kernel/qeventloop.cpp:201 #31 0xb5bdeae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #32 0xb60a1bb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #33 0x0804bfef in main (argc=1, argv=0xbfd85794) at /build/buildd/kdepim-4.3.2/kontact/src/main.cpp:218 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 180471 ***
will work better without messing the numbers. *** This bug has been marked as a duplicate of bug 180741 ***