Application that crashed: kmail Version of the application: 1.12.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: The crash happened when i deleted an email on an imap account. I didn't managed to reproduce this bug after restarting the application. System: Ubuntu 9.10 RC amd64 updates installed -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #5 0x00007f71208c9dbb in ?? () from /usr/lib/libkmailprivate.so.4 #6 0x00007f7120772c23 in ?? () from /usr/lib/libkmailprivate.so.4 #7 0x00007f712088c727 in KMMoveCommand::execute() () from /usr/lib/libkmailprivate.so.4 #8 0x00007f71208722ca in KMCommand::slotPostTransfer(KMCommand::Result) () from /usr/lib/libkmailprivate.so.4 #9 0x00007f712087c4d3 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #10 0x00007f712088d810 in KMMoveCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #11 0x00007f711f316ddc in QMetaObject::activate (sender=0x10c2ea0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1cfaf30) at kernel/qobject.cpp:3113 #12 0x00007f712086f44e in KMCommand::messagesTransfered(KMCommand::Result) () from /usr/lib/libkmailprivate.so.4 #13 0x00007f712088a648 in KMCommand::transferSelectedMsgs() () from /usr/lib/libkmailprivate.so.4 #14 0x00007f712088a86f in KMCommand::slotStart() () from /usr/lib/libkmailprivate.so.4 #15 0x00007f712087c4b6 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #16 0x00007f712088d810 in KMMoveCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #17 0x00007f711f316ddc in QMetaObject::activate (sender=0x1cd75b0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1cfaf30) at kernel/qobject.cpp:3113 #18 0x00007f711f31be1f in QSingleShotTimer::timerEvent (this=0x1cd75b0) at kernel/qtimer.cpp:298 #19 0x00007f711f310d83 in QObject::event (this=0x1cd75b0, e=0x1af6440) at kernel/qobject.cpp:1075 #20 0x00007f711f794efc in QApplicationPrivate::notify_helper (this=0xe52780, receiver=0x1cd75b0, e=0x7fff94ee5d10) at kernel/qapplication.cpp:4056 #21 0x00007f711f79c1ce in QApplication::notify (this=0x7fff94ee6180, receiver=0x1cd75b0, e=0x7fff94ee5d10) at kernel/qapplication.cpp:4021 #22 0x00007f7121557ab6 in KApplication::notify (this=0x7fff94ee6180, receiver=0x1cd75b0, event=0x7fff94ee5d10) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x00007f711f301c2c in QCoreApplication::notifyInternal (this=0x7fff94ee6180, receiver=0x1cd75b0, event=0x7fff94ee5d10) at kernel/qcoreapplication.cpp:610 #24 0x00007f711f32c862 in QCoreApplication::sendEvent (this=0xe4df40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #25 QTimerInfoList::activateTimers (this=0xe4df40) at kernel/qeventdispatcher_unix.cpp:572 #26 0x00007f711f32a25d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #27 0x00007f711659abbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #28 0x00007f711659e588 in ?? () from /lib/libglib-2.0.so.0 #29 0x00007f711659e6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #30 0x00007f711f32a1a6 in QEventDispatcherGlib::processEvents (this=0xdda930, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #31 0x00007f711f8294be in QGuiEventDispatcherGlib::processEvents (this=0x7fff94ee5030, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #32 0x00007f711f300532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #33 0x00007f711f300904 in QEventLoop::exec (this=0x7fff94ee5fb0, flags=) at kernel/qeventloop.cpp:201 #34 0x00007f711f302ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0x0000000000402fe9 in _start () This bug may be a duplicate of or related to bug 206726 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 163071 ***