Application that crashed: kontact Version of the application: 4.3.3 KDE Version: 4.3.3 (KDE 4.3.3) 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: When replying to or forwarding inline email from MacOS X users Kmail crashes with segmentation fault. This is 100% reproduceable. I can forward an example email. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x00007f3bd4b74950 in ?? () from /usr/lib/libkmailprivate.so.4 #6 0x00007f3bd4d08c6f in ?? () from /usr/lib/libkmailprivate.so.4 #7 0x00007f3bd4d0874e in ?? () from /usr/lib/libkmailprivate.so.4 #8 0x00007f3bd4a9d074 in ?? () from /usr/lib/libkmailprivate.so.4 #9 0x00007f3bd4a9d4ac in ?? () from /usr/lib/libkmailprivate.so.4 #10 0x00007f3bd4a9f94d in ?? () from /usr/lib/libkmailprivate.so.4 #11 0x00007f3bd4e4b494 in ?? () from /usr/lib/libkmailprivate.so.4 #12 0x00007f3bd4e4847d in ?? () from /usr/lib/libkmailprivate.so.4 #13 0x00007f3bd4aa809f in ?? () from /usr/lib/libkmailprivate.so.4 #14 0x00007f3bd4d265d3 in KMReplyToAllCommand::execute() () from /usr/lib/libkmailprivate.so.4 #15 0x00007f3bd4d1f4da in KMCommand::slotPostTransfer(KMCommand::Result) () from /usr/lib/libkmailprivate.so.4 #16 0x00007f3bd4d296e3 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #17 0x00007f3bea736ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #18 0x00007f3bd4d1c65e in KMCommand::messagesTransfered(KMCommand::Result) () from /usr/lib/libkmailprivate.so.4 #19 0x00007f3bd4d37858 in KMCommand::transferSelectedMsgs() () from /usr/lib/libkmailprivate.so.4 #20 0x00007f3bd4d37a7f in KMCommand::slotStart() () from /usr/lib/libkmailprivate.so.4 #21 0x00007f3bd4d296c6 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #22 0x00007f3bea736ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #23 0x00007f3bea73be1f in ?? () from /usr/lib/libQtCore.so.4 #24 0x00007f3bea730d83 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #25 0x00007f3beb041efc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #26 0x00007f3beb0491ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #27 0x00007f3bebc78e56 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #28 0x00007f3bea721c2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #29 0x00007f3bea74c862 in ?? () from /usr/lib/libQtCore.so.4 #30 0x00007f3bea74a25d in ?? () from /usr/lib/libQtCore.so.4 #31 0x00007f3be3f9cbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #32 0x00007f3be3fa0588 in ?? () from /lib/libglib-2.0.so.0 #33 0x00007f3be3fa06b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #34 0x00007f3bea74a1a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0x00007f3beb0d64be in ?? () from /usr/lib/libQtGui.so.4 #36 0x00007f3bea720532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0x00007f3bea720904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #38 0x00007f3bea722ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #39 0x0000000000403f47 in _start () This bug may be a duplicate of or related to bug 213945 Reported using DrKonqi
A full backtrace could be useful as this may be already reported. - If you can reproduce the crash at will (or you experience this regularly), can you install the "kdepim-dbg" package and post a complete backtrace here? Thanks
Changing status.
I am currently traveling in Africa and bandwidth is limited, so I cannot install kdepim-dbg. I will do so as soon as I return to Europe, which will be around 20 November. In the meantime I can provide a developer with two sample emails, each of which replicate the crash reliably. Ttm
- Are you back from your trip ? I think that devs are a bit busy so I don't know if they could receive the sample emails, but do not delete them, they could be useful at some point. Thanks!
No feedback. Closing.