Version: 1.10.0 (using KDE 4.0.98) Installed from: SuSE RPMs OS: Linux I am using KDE 4.1.00 (KDE 4.0.99 (4.1 rc1+)) "release 15" and kmail 1.10.0 in openSUSE 11.0 86_x64. I received yesterday a failure e-mail notification. As I was examining its contents, there was a file attached with the name "unnamed" and an icon with the @ symbol on it. When I clicked on this icon, kmail segfaulted. Since my ISP offers web access to my e-mail, the file that caused kmail to crash is nothing but an error trace from an MTA regarding the failed e-mail delivery and nothing suspicious. The back trace will follow.
Created attachment 26324 [details] the back trace file
[KCrash handler] #5 0x00007f91e73c170b in ?? () from /usr/lib64/libkmailprivate.so.4 #6 0x00007f91e73c37e4 in ?? () from /usr/lib64/libkmailprivate.so.4 #7 0x00007f91e7533cd5 in KMSetStatusCommand::execute () from /usr/lib64/libkmailprivate.so.4 #8 0x00007f91e752ca72 in KMCommand::slotPostTransfer () from /usr/lib64/libkmailprivate.so.4 #9 0x00007f91e7536cbe in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #10 0x00007f91e10fa4e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #11 0x00007f91e752994e in KMCommand::messagesTransfered () from /usr/lib64/libkmailprivate.so.4 #12 0x00007f91e753f379 in KMCommand::transferSelectedMsgs () from /usr/lib64/libkmailprivate.so.4 #13 0x00007f91e753f58d in KMCommand::slotStart () from /usr/lib64/libkmailprivate.so.4 #14 0x00007f91e7536cd2 in KMCommand::qt_metacall () from /usr/lib64/libkmailprivate.so.4 #15 0x00007f91e10fa4e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #16 0x00007f91e1100fdf in ?? () from /usr/lib64/libQtCore.so.4 #17 0x00007f91e10f66e3 in QObject::event () from /usr/lib64/libQtCore.so.4 #18 0x00007f91dd3a992d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #19 0x00007f91dd3afcfa in QApplication::notify () from /usr/lib64/libQtGui.so.4 #20 0x00007f91e2be6ddb in KApplication::notify () from /usr/lib64/libkdeui.so.5 #21 0x00007f91e10e8e9c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #22 0x00007f91e110f3c6 in ?? () from /usr/lib64/libQtCore.so.4 #23 0x00007f91e110f678 in QEventDispatcherUNIX::processEvents () from /usr/lib64/libQtCore.so.4 #24 0x00007f91dd42a34a in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f91e10e77f2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #26 0x00007f91e10e7985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #27 0x00007f91e10e9a25 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #28 0x000000000040309b in _start () #0 0x00007f91db8b8261 in nanosleep () from /lib64/libc.so.6
Please read the following page and provide a useful backtrace for this crash : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Indeed, the backtrace is almost useless without better debugging information. Please also attach the mail which caused the trash. I tested another mail which had a mail as an attachment, but that one worked fine. Are you using IMAP or POP3?
Hello The error appears sporadically. I access the same e-mail frequently but it didn't reoccur until now. I am using POP3 to access the e-mail. Unfortunately I can't attach the e-mail because it contains sensitive personal information. I am attaching the new trace. I hope it is helpful. Note that the new trace has been captured from KMail 1.10.0 using KDE 4.1.1 (KDE 4.1.0 (4.1 >=20080722)) "release 19.3"
Created attachment 26564 [details] 2nd trace file
#5 0x0000000000000030 in ?? () #6 0x00007f5917133994 in FolderStorage::setStatus (this=0x869010, ids=@0xb433c8, status=@0x19f12f8, toggle=false) at /usr/src/debug/kdepim-4.1.0/kmail/folderstorage.cpp:1081 #7 0x00007f59172a4db5 in KMSetStatusCommand::execute (this=0x19f12b0) at /usr/src/debug/kdepim-4.1.0/kmail/kmcommands.cpp:1674 #8 0x00007f591729db52 in KMCommand::slotPostTransfer (this=0x19f12b0, result=KMCommand::OK) at /usr/src/debug/kdepim-4.1.0/kmail/kmcommands.cpp:273 #9 0x00007f59172a7dae in KMCommand::qt_metacall (this=0x19f12b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fa4e640) at /usr/src/debug/kdepim-4.1.0/build/kmail/kmcommands.moc:86 #10 0x00007f5910e844e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #11 0x00007f591729aa1e in KMCommand::messagesTransfered (this=0xbc12b0, _t1=KMCommand::OK) at /usr/src/debug/kdepim-4.1.0/build/kmail/kmcommands.moc:100 #12 0x00007f59172b0469 in KMCommand::transferSelectedMsgs (this=0x19f12b0) at /usr/src/debug/kdepim-4.1.0/kmail/kmcommands.cpp:367 #13 0x00007f59172b067d in KMCommand::slotStart (this=0x19f12b0) at /usr/src/debug/kdepim-4.1.0/kmail/kmcommands.cpp:265 #14 0x00007f59172a7dc2 in KMCommand::qt_metacall (this=0x19f12b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1fa4e860) at /usr/src/debug/kdepim-4.1.0/build/kmail/kmcommands.moc:85 #15 0x00007f5910e844e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #16 0x00007f5910e8afdf in ?? () from /usr/lib64/libQtCore.so.4 #17 0x00007f5910e806e3 in QObject::event () from /usr/lib64/libQtCore.so.4 #18 0x00007f590d13392d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #19 0x00007f590d139cfa in QApplication::notify () from /usr/lib64/libQtGui.so.4 #20 0x00007f59129710eb in KApplication::notify () from /usr/lib64/libkdeui.so.5 #21 0x00007f5910e72e9c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #22 0x00007f5910e993c6 in ?? () from /usr/lib64/libQtCore.so.4 #23 0x00007f5910e99678 in QEventDispatcherUNIX::processEvents () from /usr/lib64/libQtCore.so.4 #24 0x00007f590d1b434a in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f5910e717f2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #26 0x00007f5910e71985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #27 0x00007f5910e73a25 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #28 0x000000000040309b in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.1.0/kmail/main.cpp:146 #0 0x00007f590b642261 in nanosleep () from /lib64/libc.so.6
The second backtrace looks similar to the one in bug 171630 , they may be related each other.
Any news related to this? Is this still happening on an updated KDE version? Thanks
*** This bug has been marked as a duplicate of bug 208778 ***