Application that crashed: kmail Version of the application: 1.12.0 KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: This might be related to the dreaded bug 163071: If you trigger an IMAP action like deleting a bunch of mails from your inbox, and exit KMail while those aren't finished yet, it will crash. After a restart, it seems like those ,essages were already copied to Trash, but weren't deleted from my inbox. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #5 0x00007fef34d7322d in KMail::ISubject::notify (this=0x2594860) at /build/buildd/kdepim-4.2.96/kmail/isubject.cpp:29 #6 0x00007fef34a5427a in KMMessage::updateBodyPart (this=0x2594790, partSpecifier= {static null = {<No data fields>}, static shared_null = {ref = {_q_value = 36899}, alloc = 0, size = 0, data = 0x7fef310d541a, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, static shared_empty = {ref = {_q_value = 457}, alloc = 0, size = 0, data = 0x7fef310d543a, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d = 0x7fff3dfcbdf0, static codecForCStrings = 0x0}, data=<value optimized out>) at /build/buildd/kdepim-4.2.96/kmail/kmmessage.cpp:3196 #7 0x00007fef34d46ac4 in KMail::ImapJob::slotGetMessageResult (this=0xe2b920, job=0x25c29a0) at /build/buildd/kdepim-4.2.96/kmail/imapjob.cpp:435 #8 0x00007fef34d49c77 in KMail::ImapJob::qt_metacall (this=0xe2b920, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff3dfcbf80) at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/imapjob.moc:82 #9 0x00007fef30df51f2 in QMetaObject::activate (sender=0x25c29a0, from_signal_index=<value optimized out>, to_signal_index=7, argv=0x23f9570) at kernel/qobject.cpp:3069 #10 0x00007fef35422512 in KJob::result (this=0xe27638, _t1=0x25c29a0) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kdecore/kjob.moc:188 #11 0x00007fef3542288f in KJob::emitResult (this=0x25c29a0) at /build/buildd/kde4libs-4.2.96/kdecore/jobs/kjob.cpp:304 #12 0x00007fef3283dd70 in KIO::SimpleJob::slotFinished (this=0x25c29a0) at /build/buildd/kde4libs-4.2.96/kio/kio/job.cpp:477 #13 0x00007fef3283e223 in KIO::TransferJob::slotFinished (this=0x25c29a0) at /build/buildd/kde4libs-4.2.96/kio/kio/job.cpp:948 #14 0x00007fef32839015 in KIO::TransferJob::qt_metacall (this=0x25c29a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff3dfcc380) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/jobclasses.moc:343 #15 0x00007fef30df51f2 in QMetaObject::activate (sender=0x10fd520, from_signal_index=<value optimized out>, to_signal_index=8, argv=0x23f9570) at kernel/qobject.cpp:3069 #16 0x00007fef328fa371 in KIO::SlaveInterface::dispatch (this=0x10fd520, _cmd=104, rawdata=<value optimized out>) at /build/buildd/kde4libs-4.2.96/kio/kio/slaveinterface.cpp:175 #17 0x00007fef328f6ec2 in KIO::SlaveInterface::dispatch (this=0x10fd520) at /build/buildd/kde4libs-4.2.96/kio/kio/slaveinterface.cpp:91 #18 0x00007fef328e9a43 in KIO::Slave::gotInput (this=0x10fd520) at /build/buildd/kde4libs-4.2.96/kio/kio/slave.cpp:322 #19 0x00007fef328ebca8 in KIO::Slave::qt_metacall (this=0x10fd520, _c=QMetaObject::InvokeMetaMethod, _id=1207988480, _a=0x7fff3dfcc7a0) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/slave.moc:76 #20 0x00007fef30df51f2 in QMetaObject::activate (sender=0x21680f0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x23f9570) at kernel/qobject.cpp:3069 #21 0x00007fef32807761 in KIO::ConnectionPrivate::dequeue (this=0x2166cb0) at /build/buildd/kde4libs-4.2.96/kio/kio/connection.cpp:82 #22 0x00007fef32807bba in KIO::Connection::qt_metacall (this=0x21680f0, _c=QMetaObject::InvokeMetaMethod, _id=1207988480, _a=0x2622bc0) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/connection.moc:73 #23 0x00007fef30def848 in QObject::event (this=0x21680f0, e=0x2230870) at kernel/qobject.cpp:1118 #24 0x00007fef3152478d in QApplicationPrivate::notify_helper (this=0xb4d360, receiver=0x21680f0, e=0x2230870) at kernel/qapplication.cpp:4084 #25 0x00007fef3152c97a in QApplication::notify (this=0x7fff3dfcd310, receiver=0x21680f0, e=0x2230870) at kernel/qapplication.cpp:4049 #26 0x00007fef359b663b in KApplication::notify (this=0x7fff3dfcd310, receiver=0x21680f0, event=0x2230870) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #27 0x00007fef30ddf75c in QCoreApplication::notifyInternal (this=0x7fff3dfcd310, receiver=0x21680f0, event=0x2230870) at kernel/qcoreapplication.cpp:602 #28 0x00007fef30de03ca in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xb19aa0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #29 0x00007fef30e091e3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #30 0x00007fef27c9220a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #31 0x00007fef27c958e0 in ?? () from /usr/lib/libglib-2.0.so.0 #32 0x00007fef27c95a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #33 0x00007fef30e08e6f in QEventDispatcherGlib::processEvents (this=0xb196d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #34 0x00007fef315bcbef in QGuiEventDispatcherGlib::processEvents (this=0xe27638, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #35 0x00007fef30dde002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1039978784}) at kernel/qeventloop.cpp:149 #36 0x00007fef30dde3cd in QEventLoop::exec (this=0x7fff3dfcd160, flags={i = 1039978864}) at kernel/qeventloop.cpp:200 #37 0x00007fef30de0694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #38 0x00000000004030db in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.96/kmail/main.cpp:146 Reported using DrKonqi
This is the same backtrace as bug 197131 / bug 153411. Thanks *** This bug has been marked as a duplicate of bug 153411 ***