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.31-14-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: If an e-mail contains n > 2 attachments, and I select, using Ctrl+click m attachments with m in [2, n-1], then KMail will crash when the select destination dir. dialog should be shown. (e.g. select 2 out of 4 attachments, choose "Save as", wait for the attachments to be downloaden (IMAP) and then KMail will crash) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 DwString::c_str (this=0x2713480, msg=<value optimized out>, partSpecifier=<value optimized out>) at ../../mimelib/mimelib/string.h:618 #6 DwMessageComponent::partId (this=0x2713480, msg=<value optimized out>, partSpecifier=<value optimized out>) at ../../mimelib/mimelib/msgcmp.h:259 #7 KMLoadPartsCommand::slotPartRetrieved (this=0x2713480, msg=<value optimized out>, partSpecifier=<value optimized out>) at ../../kmail/kmcommands.cpp:2762 #8 0x00007f68bcd69696 in KMLoadPartsCommand::qt_metacall (this=0x2713480, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff3538150) at ./kmcommands.moc:1858 #9 0x00007f68d2377ddc in QMetaObject::activate (sender=0x27138a0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113 #10 0x00007f68bcdb6d67 in KMail::FolderJob::messageUpdated (this=0x27138d8, _t1=0x23e9f20, _t2=<value optimized out>) at ./folderjob.moc:106 #11 0x00007f68bcdc2cbe in KMail::ImapJob::slotGetMessageResult (this=0x27138a0, job=<value optimized out>) at ../../kmail/imapjob.cpp:476 #12 0x00007f68bcdc704b in KMail::ImapJob::qt_metacall (this=0x27138a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff3538360) at ./imapjob.moc:82 #13 0x00007f68d2377ddc in QMetaObject::activate (sender=0x15ea910, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113 #14 0x00007f68d274daf2 in KJob::result (this=0x27138d8, _t1=0x15ea910) at ./kjob.moc:188 #15 0x00007f68d274de6f in KJob::emitResult (this=0x15ea910) at ../../kdecore/jobs/kjob.cpp:304 #16 0x00007f68d07d6d93 in KIO::SimpleJob::slotFinished (this=0x15ea910) at ../../kio/kio/job.cpp:477 #17 0x00007f68d07d7253 in KIO::TransferJob::slotFinished (this=0x15ea910) at ../../kio/kio/job.cpp:948 #18 0x00007f68d07d5b61 in KIO::TransferJob::qt_metacall (this=0x15ea910, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff3538780) at ./jobclasses.moc:343 #19 0x00007f68d2377ddc in QMetaObject::activate (sender=0xc59560, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113 #20 0x00007f68d0897a81 in KIO::SlaveInterface::dispatch (this=0xc59560, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #21 0x00007f68d0894333 in KIO::SlaveInterface::dispatch (this=0xc59560) at ../../kio/kio/slaveinterface.cpp:91 #22 0x00007f68d088714d in KIO::Slave::gotInput (this=0xc59560) at ../../kio/kio/slave.cpp:322 #23 0x00007f68d088926c in KIO::Slave::qt_metacall (this=0xc59560, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff3538b40) at ./slave.moc:76 #24 0x00007f68d2377ddc in QMetaObject::activate (sender=0xc555d0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113 #25 0x00007f68d07a3f57 in KIO::ConnectionPrivate::dequeue (this=0x15243e0) at ../../kio/kio/connection.cpp:82 #26 0x00007f68d07a407d in KIO::Connection::qt_metacall (this=0xc555d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x3eb0910) at ./connection.moc:73 #27 0x00007f68d23720f9 in QObject::event (this=0xc555d0, e=0x243feb0) at kernel/qobject.cpp:1111 #28 0x00007f68d2c82efc in QApplicationPrivate::notify_helper (this=0x7e4ac0, receiver=0xc555d0, e=0x243feb0) at kernel/qapplication.cpp:4056 #29 0x00007f68d2c8a1ce in QApplication::notify (this=0x7ffff3539500, receiver=0xc555d0, e=0x243feb0) at kernel/qapplication.cpp:4021 #30 0x00007f68d38b9ab6 in KApplication::notify (this=0x7ffff3539500, receiver=0xc555d0, event=0x243feb0) at ../../kdeui/kernel/kapplication.cpp:302 #31 0x00007f68d2362c2c in QCoreApplication::notifyInternal (this=0x7ffff3539500, receiver=0xc555d0, event=0x243feb0) at kernel/qcoreapplication.cpp:610 #32 0x00007f68d236380a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x7b6190) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x7b6190) at kernel/qcoreapplication.cpp:1247 #34 0x00007f68d238b533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #35 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210 #36 0x00007f68cbbdcbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #37 0x00007f68cbbe0588 in ?? () from /lib/libglib-2.0.so.0 #38 0x00007f68cbbe06b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #39 0x00007f68d238b1a6 in QEventDispatcherGlib::processEvents (this=0x7edb80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #40 0x00007f68d2d174be in QGuiEventDispatcherGlib::processEvents (this=0x27138d8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #41 0x00007f68d2361532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #42 0x00007f68d2361904 in QEventLoop::exec (this=0x7ffff3539440, flags=) at kernel/qeventloop.cpp:201 #43 0x00007f68d2363ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #44 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 212970 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 136145 ***