Bug 203089

Summary: Crashed while marking mail as spam/ham on IMAP account
Product: [Unmaintained] kmail Reporter: benno.dreissig
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description benno.dreissig 2009-08-08 15:59:34 UTC 
Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-5-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
I was marking mails as spam/ham one by one on an IMAP Account when it crashed.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f96cd2ff750 (LWP 7188))]

Thread 2 (Thread 0x7f96b2548910 (LWP 7248)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007f96ca9ff4fb in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x3572518, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x3572518, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f96c856077c in QHostInfoAgent::run (this=0x3572500) at kernel/qhostinfo.cpp:260
#4  0x00007f96ca9fe445 in QThreadPrivate::start (arg=0x3572500) at thread/qthread_unix.cpp:188
#5  0x00007f96c553aa04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007f96ca1e75fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f96cd2ff750 (LWP 7188)):
[KCrash Handler]
#5  QBasicAtomicInt::ref (this=0x24ed050) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  QList (this=0x24ed050) at /usr/include/qt4/QtCore/qlist.h:111
#7  KMail::FolderJob::msgList (this=0x24ed050) at ../../kmail/folderjob.cpp:120
#8  0x00007f96cbf51ad3 in KMAcctImap::ignoreJobsForMessage (this=0x35be050, msg=0x37f8bb0) at ../../kmail/kmacctimap.cpp:215
#9  0x00007f96cc067d97 in KMCommand::transferSelectedMsgs (this=0x3777600) at ../../kmail/kmcommands.cpp:333
#10 0x00007f96cc06829f in KMCommand::slotStart (this=0x3777600) at ../../kmail/kmcommands.cpp:265
#11 0x00007f96cc059886 in KMCommand::qt_metacall (this=0x3777600, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff33f4fad0) at ./kmcommands.moc:86
#12 0x00007f96caaf9e5c in QMetaObject::activate (sender=0x37e77a0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x379fdb0) at kernel/qobject.cpp:3113
#13 0x00007f96caafee9f in QSingleShotTimer::timerEvent (this=0x37e77a0) at kernel/qtimer.cpp:298
#14 0x00007f96caaf3e03 in QObject::event (this=0x37e77a0, e=0x24ed050) at kernel/qobject.cpp:1075
#15 0x00007f96caf7768c in QApplicationPrivate::notify_helper (this=0x246c960, receiver=0x37e77a0, e=0x7fff33f500e0) at kernel/qapplication.cpp:4056
#16 0x00007f96caf7e95e in QApplication::notify (this=0x7fff33f50530, receiver=0x37e77a0, e=0x7fff33f500e0) at kernel/qapplication.cpp:4021
#17 0x00007f96ccd2b4d6 in KApplication::notify (this=0x7fff33f50530, receiver=0x37e77a0, event=0x7fff33f500e0) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x00007f96caae4cac in QCoreApplication::notifyInternal (this=0x7fff33f50530, receiver=0x37e77a0, event=0x7fff33f500e0) at kernel/qcoreapplication.cpp:610
#19 0x00007f96cab0f942 in QCoreApplication::sendEvent (this=0x246fda0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x246fda0) at kernel/qeventdispatcher_unix.cpp:572
#21 0x00007f96cab0d2dd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#22 0x00007f96c21b3a8e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007f96c21b7458 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f96c21b7580 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007f96cab0d226 in QEventDispatcherGlib::processEvents (this=0x24376e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#26 0x00007f96cb00bafe in QGuiEventDispatcherGlib::processEvents (this=0x7fff33f4f870, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x00007f96caae35b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#28 0x00007f96caae3984 in QEventLoop::exec (this=0x7fff33f50380, flags=) at kernel/qeventloop.cpp:201
#29 0x00007f96caae5b39 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#30 0x0000000000402fe9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-08 16:45:03 UTC 
This is likely to be bug 163071. Thanks
Comment 2 benno.dreissig 2009-08-08 17:15:14 UTC 
Could be. But I played around a bit.

It also happens if I just mark ham. And even if its only 2 messages being marked as ham. Though, I don't know if the messages get deleted, reviewed and uploaded after. They definitely disappear from the message window for a short time and reappear then. However, I found another weird thing happening.

I marked multiple messages (139) from my spam folder on the IMAP Account at once as spam. The messages got downloaded one by one - pretty fast - and moved to the trash after. But now that this little dialog appeared telling me whats happening (downloading message x/139), KMail doesn't crash anymore when marking spam/ham one by one.
Comment 3 benno.dreissig 2009-08-08 17:18:17 UTC 
I meant "now AFTER this little dialog appeared". Kmail didn't crash when marking messages spam/ham one by one AFTER this mass-marking.

It did again when I restarted it.

Sorry.
Comment 4 Christophe Marin 2009-08-09 12:11:33 UTC 

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