Bug 200022

Summary: Kmail crashes while deleting a message
Product: [Unmaintained] kmail Reporter: loxza
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: 1.11.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description loxza 2009-07-13 12:58:18 UTC
Version:           1.11.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Quite often, while trying to delete an unread message from an IMAP folder, the application crashes. The backtrace I get is the following one:

(lots of "(no debugging symbols found)")
0xb7f59430 in __kernel_vsyscall ()
[Current thread is 0 (process 16314)]

Thread 1 (Thread 0xb3bc4b40 (LWP 16314)):
#0  0xb7f59430 in __kernel_vsyscall ()
#1  0xb5b5b7a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5b5b5be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7e028b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7e03274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb758156d in ?? () from /usr/lib/libkmailprivate.so.4
#7  0xb73fad9b in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb74139e5 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb7536cc6 in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so.4
#10 0xb751a322 in KMCommand::slotPostTransfer () from /usr/lib/libkmailprivate.so.4
#11 0xb7525d74 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#12 0xb7538cba in KMMoveCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#13 0xb7538d82 in KMDeleteMsgCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#14 0xb5ea4ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb5ea5932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7516993 in KMCommand::messagesTransfered () from /usr/lib/libkmailprivate.so.4
#17 0xb753502c in KMCommand::transferSelectedMsgs () from /usr/lib/libkmailprivate.so.4
#18 0xb753528f in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.4
#19 0xb7525d83 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#20 0xb7538cba in KMMoveCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#21 0xb7538d82 in KMDeleteMsgCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#22 0xb5ea4ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb5ea5932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb5eaa0a7 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb5eaa1cc in ?? () from /usr/lib/libQtCore.so.4
#26 0xb5e9f15f in QObject::event () from /usr/lib/libQtCore.so.4
#27 0xb613be9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#28 0xb614419e in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0xb7d9294d in KApplication::notify () from /usr/lib/libkdeui.so.5
#30 0xb5e8ea3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#31 0xb5ebdd71 in ?? () from /usr/lib/libQtCore.so.4
#32 0xb5eba4e0 in ?? () from /usr/lib/libQtCore.so.4
#33 0xb42c6b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb42ca0eb in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb42ca268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb5eba438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb61dd365 in ?? () from /usr/lib/libQtGui.so.4
#38 0xb5e8d06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0xb5e8d4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0xb5e8f959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0xb613bd17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#42 0x0804a7a0 in _start ()
#0  0xb7f59430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-07-13 20:18:53 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdepim-dbg" package. Thanks
Comment 2 Christophe Marin 2009-07-18 17:47:00 UTC
Changing the bug status until we get a backtrace (see comment #2)
Comment 3 loxza 2009-08-06 09:37:23 UTC
I have been able to reproduce it one more time. Tha crash was produced while trying to delete a message that had not yet been displayed in the message content view.
Here is the backtrace:

Aplicación: KMail (kmail), señal SIGSEGV

Thread 1 (Thread 0xb3d21b40 (LWP 4249)):
[KCrash Handler]
#6  KMail::FolderJob::msgList (this=0x350031) at /usr/include/qt4/QtCore/qlist.h:111
#7  0xb7557d9b in KMAcctImap::ignoreJobsForMessage (this=0x87538c8, msg=0x9505218) at /build/buildd/kdepim-4.2.2/kmail/kmacctimap.cpp:215
#8  0xb75709e5 in KMFolderImap::ignoreJobsForMessage (this=0x8777288, msg=0x9505218) at /build/buildd/kdepim-4.2.2/kmail/kmfolderimap.cpp:1562
#9  0xb7693cc6 in KMMoveCommand::execute (this=0x93ab260) at /build/buildd/kdepim-4.2.2/kmail/kmcommands.cpp:2086
#10 0xb7677322 in KMCommand::slotPostTransfer (this=0x93ab260, result=KMCommand::OK) at /build/buildd/kdepim-4.2.2/kmail/kmcommands.cpp:276
#11 0xb7682d74 in KMCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfed3e5c) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:87
#12 0xb7695cba in KMMoveCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfed3e5c) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#13 0xb7695d82 in KMDeleteMsgCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfed3e5c) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1758
#14 0xb6001ca8 in QMetaObject::activate (sender=0x93ab260, from_signal_index=4, to_signal_index=4, argv=0xbfed3e5c) at kernel/qobject.cpp:3069
#15 0xb6002932 in QMetaObject::activate (sender=0x93ab260, m=0xb7afd9b4, local_signal_index=0, argv=0xbfed3e5c) at kernel/qobject.cpp:3143
#16 0xb7673993 in KMCommand::messagesTransfered (this=0x93ab260, _t1=KMCommand::OK) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:102
#17 0xb769202c in KMCommand::transferSelectedMsgs (this=0x93ab260) at /build/buildd/kdepim-4.2.2/kmail/kmcommands.cpp:370
#18 0xb769228f in KMCommand::slotStart (this=0x93ab260) at /build/buildd/kdepim-4.2.2/kmail/kmcommands.cpp:268
#19 0xb7682d83 in KMCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfed4058) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:86
#20 0xb7695cba in KMMoveCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfed4058) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#21 0xb7695d82 in KMDeleteMsgCommand::qt_metacall (this=0x93ab260, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfed4058) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmcommands.moc:1758
#22 0xb6001ca8 in QMetaObject::activate (sender=0x9ca3250, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#23 0xb6002932 in QMetaObject::activate (sender=0x9ca3250, m=0xb60dd908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#24 0xb60070a7 in QSingleShotTimer::timeout (this=0x9ca3250) at .moc/release-shared/qtimer.moc:76
#25 0xb60071cc in QSingleShotTimer::timerEvent (this=0x9ca3250) at kernel/qtimer.cpp:298
#26 0xb5ffc15f in QObject::event (this=0x9ca3250, e=0xbfed44dc) at kernel/qobject.cpp:1082
#27 0xb6298e9c in QApplicationPrivate::notify_helper (this=0x85b5660, receiver=0x9ca3250, e=0xbfed44dc) at kernel/qapplication.cpp:4084
#28 0xb62a119e in QApplication::notify (this=0xbfed47f8, receiver=0x9ca3250, e=0xbfed44dc) at kernel/qapplication.cpp:3631
#29 0xb7eef94d in KApplication::notify (this=0xbfed47f8, receiver=0x9ca3250, event=0xbfed44dc) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#30 0xb5feba3b in QCoreApplication::notifyInternal (this=0xbfed47f8, receiver=0x9ca3250, event=0xbfed44dc) at kernel/qcoreapplication.cpp:602
#31 0xb601ad71 in QTimerInfoList::activateTimers (this=0x85b7e44) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#32 0xb60174e0 in timerSourceDispatch (source=0x85b7e10) at kernel/qeventdispatcher_glib.cpp:164
#33 0xb4423b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb44270eb in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb4427268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb6017438 in QEventDispatcherGlib::processEvents (this=0x85655a8, flags={i = -1074969000}) at kernel/qeventdispatcher_glib.cpp:323
#37 0xb633a365 in QGuiEventDispatcherGlib::processEvents (this=0x85655a8, flags={i = -1074968952}) at kernel/qguieventdispatcher_glib.cpp:202
#38 0xb5fea06a in QEventLoop::processEvents (this=0xbfed4700, flags={i = -1074968888}) at kernel/qeventloop.cpp:149
#39 0xb5fea4aa in QEventLoop::exec (this=0xbfed4700, flags={i = -1074968824}) at kernel/qeventloop.cpp:200
#40 0xb5fec959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#41 0xb6298d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#42 0x0804a7a0 in main (argc=) at /build/buildd/kdepim-4.2.2/kmail/main.cpp:146
Comment 4 Dario Andres 2009-08-07 21:49:02 UTC
Thanks for the backtrace. Merging with bug 163071.

*** This bug has been marked as a duplicate of bug 163071 ***