*** Bug 163775 has been marked as a duplicate of this bug. ***

Oops, duplicated my own bug - sorry for the noise :) (And would someone please fix the search function in Bugzilla?)

*** Bug 168848 has been marked as a duplicate of this bug. ***

*** Bug 170296 has been marked as a duplicate of this bug. ***

Confirming as I just got the same backtrace as in (my) bugreport #168848 which was marked as a duplicate of this one (KDE version ~4.1.68)

What I did:

I deleted a (unread) message from my IMAP inbox. While it was being deleted I went over several other unread mails in the same folder (thereby marking them read) and before the deletion of the first message finished, I hit the delete button on yet another unread message in the same inbox.

The backtrace was:

#6  0x464d4b28 in ?? ()
#7  0xb1c5dc72 in KMAcctImap::ignoreJobsForMessage (this=0x83eb220, msg=0x87203b0) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmacctimap.cpp:217
#8  0xb1c7051b in KMFolderImap::ignoreJobsForMessage (this=0x845af18, msg=0x87203b0) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmfolderimap.cpp:1543
#9  0xb1d3277a in KMMoveCommand::execute (this=0x8bc3560) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmcommands.cpp:2089
#10 0xb1d40bc5 in KMCommand::slotPostTransfer (this=0x8bc3560, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmcommands.cpp:273
#11 0xb1d40dde in KMCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf9c08bc) at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:86
#12 0xb1d41326 in KMMoveCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c08bc)
    at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:1662
#13 0xb1d413da in KMDeleteMsgCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c08bc)
    at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:1712
#14 0xb7ed64e1 in QMetaObject::activate (sender=0x8bc3560, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xbf9c08bc) at kernel/qobject.cpp:3028
#15 0xb7ed83d8 in QMetaObject::activate (sender=0x8bc3560, m=0xb1fbca14, local_signal_index=0, argv=0xbf9c08bc) at kernel/qobject.cpp:3098
#16 0xb1d28e8d in KMCommand::messagesTransfered (this=0x8bc3560, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:100
#17 0xb1d40ae7 in KMCommand::transferSelectedMsgs (this=0x8bc3560) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmcommands.cpp:367
#18 0xb1d41e08 in KMCommand::slotStart (this=0x8bc3560) at /var/tmp/portage/kde-base/kmail-9999/work/kmail/kmail/kmcommands.cpp:265
#19 0xb1d40dc4 in KMCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf9c0ad8) at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:85
#20 0xb1d41326 in KMMoveCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c0ad8)
    at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:1662
#21 0xb1d413da in KMDeleteMsgCommand::qt_metacall (this=0x8bc3560, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c0ad8)
    at /var/tmp/portage/kde-base/kmail-9999/work/kmail_build/kmail/kmcommands.moc:1712
#22 0xb7ed64e1 in QMetaObject::activate (sender=0x8b2a5f0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3028
#23 0xb7ed83d8 in QMetaObject::activate (sender=0x8b2a5f0, m=0xb7fa39e4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3098
#24 0xb7edc005 in QSingleShotTimer::timeout (this=0x8b2a5f0) at .moc/debug-shared/qtimer.moc:74
#25 0xb7edc106 in QSingleShotTimer::timerEvent (this=0x8b2a5f0) at kernel/qtimer.cpp:300
#26 0xb7ecf969 in QObject::event (this=0x8b2a5f0, e=0xbf9c0f8c) at kernel/qobject.cpp:1117
#27 0xb5a22fab in QApplicationPrivate::notify_helper (this=0x8066200, receiver=0x8b2a5f0, e=0xbf9c0f8c) at kernel/qapplication.cpp:3809
#28 0xb5a29ae5 in QApplication::notify (this=0xbf9c1348, receiver=0x8b2a5f0, e=0xbf9c0f8c) at kernel/qapplication.cpp:3399
#29 0xb7a0f2b1 in KApplication::notify (this=0xbf9c1348, receiver=0x8b2a5f0, event=0xbf9c0f8c) at /var/tmp/portage/kde-base/kdelibs-9999/work/kdelibs-9999/kdeui/kernel/kapplication.cpp:307
#30 0xb7ebfb21 in QCoreApplication::notifyInternal (this=0xbf9c1348, receiver=0x8b2a5f0, event=0xbf9c0f8c) at kernel/qcoreapplication.cpp:593
#31 0xb7eec36e in QTimerInfoList::activateTimers (this=0x8067a34) at kernel/qcoreapplication.h:215
#32 0xb7eec532 in QEventDispatcherUNIX::processEvents (this=0x80670f0, flags={i = -1080290772}) at kernel/qeventdispatcher_unix.cpp:899
#33 0xb5ab864f in QEventDispatcherX11::processEvents (this=0x80670f0, flags={i = -1080290712}) at kernel/qeventdispatcher_x11.cpp:154
#34 0xb7ebe6b0 in QEventLoop::processEvents (this=0xbf9c12e0, flags={i = -1080290648}) at kernel/qeventloop.cpp:149
#35 0xb7ebe852 in QEventLoop::exec (this=0xbf9c12e0, flags={i = -1080290584}) at kernel/qeventloop.cpp:200
#36 0xb7ec0c6f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#37 0xb5a22d43 in QApplication::exec () at kernel/qapplication.cpp:3337
#38 0x0804b901 in main (argc=3, argv=0xbf9c1504) at /var/tmp/portage/kde-base/kontact-9999/work/kontact/kontact/src/main.cpp:218

*** Bug 173552 has been marked as a duplicate of this bug. ***

*** Bug 172936 has been marked as a duplicate of this bug. ***

*** Bug 180666 has been marked as a duplicate of this bug. ***

*** Bug 180824 has been marked as a duplicate of this bug. ***

*** Bug 182562 has been marked as a duplicate of this bug. ***

As stated in bug 182556 this is still happening in KDE4.2.0

*** Bug 183147 has been marked as a duplicate of this bug. ***

*** Bug 183134 has been marked as a duplicate of this bug. ***

*** Bug 183414 has been marked as a duplicate of this bug. ***

*** Bug 183294 has been marked as a duplicate of this bug. ***

*** Bug 186041 has been marked as a duplicate of this bug. ***

*** Bug 186167 has been marked as a duplicate of this bug. ***

*** Bug 182152 has been marked as a duplicate of this bug. ***

*** Bug 187950 has been marked as a duplicate of this bug. ***

*** Bug 188013 has been marked as a duplicate of this bug. ***

*** Bug 188532 has been marked as a duplicate of this bug. ***

*** Bug 190069 has been marked as a duplicate of this bug. ***

*** Bug 191165 has been marked as a duplicate of this bug. ***

*** Bug 192078 has been marked as a duplicate of this bug. ***

*** Bug 192662 has been marked as a duplicate of this bug. ***

FYI, still crashing with KDE 4.2.3 and Qt 4.5.1
The backtrace looks like the same, AFAIK

Application: KMail (kmail), signal SIGSEGV

Thread 1 (Thread 0xb3ba3b40 (LWP 1009)):
[KCrash Handler]
#6  KMail::FolderJob::msgList (this=0x2d0039) at /usr/include/qt4/QtCore/qlist.h:111
#7  0xb739dafb in KMAcctImap::ignoreJobsForMessage (this=0x8a5ed30, msg=0x9759398) at /build/buildd/kdepim-4.2.3/kmail/kmacctimap.cpp:215
#8  0xb73b67e5 in KMFolderImap::ignoreJobsForMessage (this=0x87f74c8, msg=0x9759398) at /build/buildd/kdepim-4.2.3/kmail/kmfolderimap.cpp:1562
#9  0xb74d9ee6 in KMMoveCommand::execute (this=0x9abe790) at /build/buildd/kdepim-4.2.3/kmail/kmcommands.cpp:2089
#10 0xb74bd342 in KMCommand::slotPostTransfer (this=0x9abe790, result=KMCommand::OK) at /build/buildd/kdepim-4.2.3/kmail/kmcommands.cpp:276
#11 0xb74c8f94 in KMCommand::qt_metacall (this=0x9abe790, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb1998c) at /build/buildd/kdepim-4.2.3/obj-i486-linux-gnu/kmail/kmcommands.moc:87
#12 0xb74dbeda in KMMoveCommand::qt_metacall (this=0x9abe790, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb1998c) at /build/buildd/kdepim-4.2.3/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#13 0xb5e67a58 in QMetaObject::activate (sender=0x9abe790, from_signal_index=4, to_signal_index=4, argv=0xbfb1998c) at kernel/qobject.cpp:3120
#14 0xb5e686e2 in QMetaObject::activate (sender=0x9abe790, m=0xb79449b4, local_signal_index=0, argv=0xbfb1998c) at kernel/qobject.cpp:3194
#15 0xb74b99b3 in KMCommand::messagesTransfered (this=0x9abe790, _t1=KMCommand::OK) at /build/buildd/kdepim-4.2.3/obj-i486-linux-gnu/kmail/kmcommands.moc:102
#16 0xb74d86cc in KMCommand::transferSelectedMsgs (this=0x9abe790) at /build/buildd/kdepim-4.2.3/kmail/kmcommands.cpp:370
#17 0xb74d892f in KMCommand::slotStart (this=0x9abe790) at /build/buildd/kdepim-4.2.3/kmail/kmcommands.cpp:268
#18 0xb74c8fa3 in KMCommand::qt_metacall (this=0x9abe790, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb19b68) at /build/buildd/kdepim-4.2.3/obj-i486-linux-gnu/kmail/kmcommands.moc:86
#19 0xb74dbeda in KMMoveCommand::qt_metacall (this=0x9abe790, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb19b68) at /build/buildd/kdepim-4.2.3/obj-i486-linux-gnu/kmail/kmcommands.moc:1706
#20 0xb5e67a58 in QMetaObject::activate (sender=0x9641ec0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120
#21 0xb5e686e2 in QMetaObject::activate (sender=0x9641ec0, m=0xb5f43908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#22 0xb5e6ce57 in QSingleShotTimer::timeout (this=0x9641ec0) at .moc/release-shared/qtimer.moc:76
#23 0xb5e6cf7c in QSingleShotTimer::timerEvent (this=0x9641ec0) at kernel/qtimer.cpp:298
#24 0xb5e61f0f in QObject::event (this=0x9641ec0, e=0xbfb19fec) at kernel/qobject.cpp:1082
#25 0xb60dcbcc in QApplicationPrivate::notify_helper (this=0x85ea860, receiver=0x9641ec0, e=0xbfb19fec) at kernel/qapplication.cpp:4057
#26 0xb60e4ede in QApplication::notify (this=0xbfb1a308, receiver=0x9641ec0, e=0xbfb19fec) at kernel/qapplication.cpp:3604
#27 0xb7d37e5d in KApplication::notify (this=0xbfb1a308, receiver=0x9641ec0, event=0xbfb19fec) at /build/buildd/kde4libs-4.2.3/kdeui/kernel/kapplication.cpp:307
#28 0xb5e517ab in QCoreApplication::notifyInternal (this=0xbfb1a308, receiver=0x9641ec0, event=0xbfb19fec) at kernel/qcoreapplication.cpp:610
#29 0xb5e80b31 in QTimerInfoList::activateTimers (this=0x85eb8bc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#30 0xb5e7d280 in timerSourceDispatch (source=0x85eb888) at kernel/qeventdispatcher_glib.cpp:164
#31 0xb42a3b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb42a70eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb42a7268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb5e7d1d8 in QEventDispatcherGlib::processEvents (this=0x85cf548, flags={i = -1078877848}) at kernel/qeventdispatcher_glib.cpp:324
#35 0xb617e765 in QGuiEventDispatcherGlib::processEvents (this=0x85cf548, flags={i = -1078877800}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb5e4fdda in QEventLoop::processEvents (this=0xbfb1a210, flags={i = -1078877736}) at kernel/qeventloop.cpp:149
#37 0xb5e5021a in QEventLoop::exec (this=0xbfb1a210, flags={i = -1078877672}) at kernel/qeventloop.cpp:200
#38 0xb5e526c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0xb60dca47 in QApplication::exec () at kernel/qapplication.cpp:3526
#40 0x0804a7a0 in main (argc=) at /build/buildd/kdepim-4.2.3/kmail/main.cpp:146

*** Bug 193366 has been marked as a duplicate of this bug. ***

*** Bug 193642 has been marked as a duplicate of this bug. ***

*** Bug 193667 has been marked as a duplicate of this bug. ***

*** Bug 195598 has been marked as a duplicate of this bug. ***

*** Bug 195870 has been marked as a duplicate of this bug. ***

Confirmed on 4.2.4 (bumped version to 1.11.4).

*** Bug 195945 has been marked as a duplicate of this bug. ***

I am noticing this crash not only on INBOX , I have a folder spam in my local folders to which I am redirecting SPAM mails. If I select to move all the messages in the folder to Trash it crashes, though the deletion is successful.

Yes, this happens on any folder.

From quite a lot of experience with this bug, my hunch is that it might be to do with a message being deleted while it's being downloaded. This isn't a problem per-se, but if the download is triggered by a request to display it in the preview pane, I think, then when the preview pane tries to display it, the message no longer exists.

Is this a possibility?

(In reply to comment #35)
> Yes, this happens on any folder.
> 
> ... it might be to
> do with a message being deleted while it's being downloaded. ...
> 
> Is this a possibility?

not only this, it crash when you delete a message if there is already delete queue running (if you delete a lot of messages and delete another one before first selected messages are deleted)... at least for imap folders

*** Bug 196478 has been marked as a duplicate of this bug. ***

*** Bug 197692 has been marked as a duplicate of this bug. ***

*** Bug 198302 has been marked as a duplicate of this bug. ***

On Tuesday 30 Jun 2009 12:09:04 pm Christophe Giboudeaux wrote:
> https://bugs.kde.org/show_bug.cgi?id=163071
>
>
> Christophe Giboudeaux <cgiboudeaux@gmail.com> changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- CC|                            |marc@links2linux.de
>
>
>
>
> --- Comment #39 from Christophe Giboudeaux <cgiboudeaux gmail com> 
> 2009-06-30 08:39:02 --- *** Bug 198302 has been marked as a duplicate of
> this bug. ***
I don't see this bug anymore with kde 4.2.90

On Tuesday 30 June 2009 07:51:04 Jithin Emmanuel wrote:
> I don't see this bug anymore with kde 4.2.90

I haven't observed it since I've been using the pre-4.3 snapshots either (I'm 
now on 4.2.95).

However, I would urge some caution, since for me at least, it's been fairly 
fickle to trigger.

Well done though - I like the new moving between messages action. Seems much 
faster.

If this is really a duplicate of #198302, then its NOT fixed in 4.2.91 ...

Ok, fixed for me on 4.2.95

(In reply to comment #43)
> Ok, fixed for me on 4.2.95

I can still reproduce the crash using 4.2.95 when deleting emails from imap folder and delete another one before queue is finished.

(In reply to comment #44)
> (In reply to comment #43)
> > Ok, fixed for me on 4.2.95
> 
> I can still reproduce the crash using 4.2.95 when deleting emails from imap
> folder and delete another one before queue is finished.

taking back, this was unrelated coincidence... backtrace is looking different

it seems it's related to email containing calendar invitation:

#2  <signal handler called>
#3  0x00007f02f9368ad0 in QString::operator=(QString const&) () from /usr/lib64/libQtCore.so.4
#4  0x00007f02fac87a5f in invitationsDetailsIncidence(struct KCal::Incidence *, bool) (incidence=0x2f6f810, noHtmlMode=<value optimized out>) at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:715
#5  0x00007f02fac90a16 in invitationDetailsEvent(struct KCal::Event *, bool) (event=0x2f6f810, noHtmlMode=true) at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:827
#6  0x00007f02fac94555 in KCal::IncidenceFormatter::InvitationBodyVisitor::visit (this=0x7fff361972a0, event=0x7fff36196d80) at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:1272
#7  0x00007f02fac8005f in KCal::IncidenceFormatter::ScheduleMessageVisitor::act (msg=<value optimized out>, incidence=<value optimized out>, this=<value optimized out>) at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:1227
#8  formatICalInvitationHelper(QString, struct KCal::Calendar *, KCal::InvitationFormatterHelper *, bool) (msg=<value optimized out>, incidence=<value optimized out>, this=<value optimized out>) at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:1510
#9  0x00007f02fac80f04 in KCal::IncidenceFormatter::formatICalInvitationNoHtml (invitation=<value optimized out>, mCalendar=0x1, helper=0x233a670)
    at /usr/src/debug/kdepimlibs-4.2.95/kcal/incidenceformatter.cpp:1664
#10 0x00007f02dbdf3445 in (anonymous namespace)::Formatter::format(struct KMail::Interface::BodyPart *, struct KMail::HtmlWriter *) (this=<value optimized out>,
    bodyPart=<value optimized out>, writer=0x22fd0e0) at /usr/src/debug/kdepim-4.2.95/plugins/kmail/bodypartformatter/text_calendar.cpp:161
#11 0x00007f02fbbe3699 in KMail::ObjectTreeParser::parseObjectTree (this=0x7fff36197b20, node=0x30c5ee0) at /usr/src/debug/kdepim-4.2.95/kmail/objecttreeparser.cpp:268
#12 0x00007f02fbbe4135 in KMail::ObjectTreeParser::stdChildHandling (this=0x7fff36197e70, child=0x3156fe0) at /usr/src/debug/kdepim-4.2.95/kmail/objecttreeparser.cpp:1136
...

I can't reproduce this bug as such right now with 4.2.95

closing as fixed then

I got this again with 4.3.60 (r986576).  I moved a set of emails between folders on an IMAP account, then moved another set (between the same folders) while the first operation was still happening.  I did this a couple of times before the crash happened.



 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fbd71e301f6 in QList (this=0x7fffb82ea310, l=@0x720000009f000010) at /home/kde-devel/qt/include/QtCore/../../../kde-qt/src/corelib/tools/qlist.h:111
#6  0x00007fbd72095224 in KMail::FolderJob::msgList (this=0x720000009f000000) at /home/kde-devel/src/KDE/kdepim/kmail/folderjob.cpp:120
#7  0x00007fbd71f30833 in KMAcctImap::ignoreJobsForMessage (this=0x2498da0, msg=0x35d54c0) at /home/kde-devel/src/KDE/kdepim/kmail/kmacctimap.cpp:215
#8  0x00007fbd71f4efad in KMFolderImap::ignoreJobsForMessage (this=0x21fbca0, msg=0x35d54c0) at /home/kde-devel/src/KDE/kdepim/kmail/kmfolderimap.cpp:1564
#9  0x00007fbd72043d34 in KMMoveCommand::execute (this=0x36ba410) at /home/kde-devel/src/KDE/kdepim/kmail/kmcommands.cpp:2144
#10 0x00007fbd720357d4 in KMCommand::slotPostTransfer (this=0x36ba410, result=KMCommand::OK) at /home/kde-devel/src/KDE/kdepim/kmail/kmcommands.cpp:277
#11 0x00007fbd720506b7 in KMCommand::qt_metacall (this=0x36ba410, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7fffb82ea710) at /home/kde-devel/build/KDE/kdepim/kmail/kmcommands.moc:87
#12 0x00007fbd72052145 in KMMoveCommand::qt_metacall (this=0x36ba410, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fffb82ea710) at /home/kde-devel/build/KDE/kdepim/kmail/kmcommands.moc:1749
#13 0x00007fbd6f66dee9 in QMetaObject::activate (sender=0x36ba410, from_signal_index=4, to_signal_index=4, argv=0x7fffb82ea710) at /home/kde-devel/kde-qt/src/corelib/kernel/qobject.cpp:3119
#14 0x00007fbd6f66e28d in QMetaObject::activate (sender=0x36ba410, m=0x7fbd726837c0, local_signal_index=0, argv=0x7fffb82ea710) at /home/kde-devel/kde-qt/src/corelib/kernel/qobject.cpp:3193
#15 0x00007fbd7205074a in KMCommand::messagesTransfered (this=0x36ba410, _t1=KMCommand::OK) at /home/kde-devel/build/KDE/kdepim/kmail/kmcommands.moc:102
#16 0x00007fbd72036028 in KMCommand::transferSelectedMsgs (this=0x36ba410) at /home/kde-devel/src/KDE/kdepim/kmail/kmcommands.cpp:371
#17 0x00007fbd72035761 in KMCommand::slotStart (this=0x36ba410) at /home/kde-devel/src/KDE/kdepim/kmail/kmcommands.cpp:269
#18 0x00007fbd7205069a in KMCommand::qt_metacall (this=0x36ba410, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffb82ea9a0) at /home/kde-devel/build/KDE/kdepim/kmail/kmcommands.moc:86
#19 0x00007fbd72052145 in KMMoveCommand::qt_metacall (this=0x36ba410, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffb82ea9a0) at /home/kde-devel/build/KDE/kdepim/kmail/kmcommands.moc:1749
#20 0x00007fbd6f66dee9 in QMetaObject::activate (sender=0x2da1b10, from_signal_index=4, to_signal_index=4, argv=0x0) at /home/kde-devel/kde-qt/src/corelib/kernel/qobject.cpp:3119
#21 0x00007fbd6f66e28d in QMetaObject::activate (sender=0x2da1b10, m=0x7fbd6f98b9a0, local_signal_index=0, argv=0x0) at /home/kde-devel/kde-qt/src/corelib/kernel/qobject.cpp:3193
#22 0x00007fbd6f677b69 in QSingleShotTimer::timeout (this=0x2da1b10) at .moc/debug-shared/qtimer.moc:76
#23 0x00007fbd6f677a6b in QSingleShotTimer::timerEvent (this=0x2da1b10) at /home/kde-devel/kde-qt/src/corelib/kernel/qtimer.cpp:298
#24 0x00007fbd6f669841 in QObject::event (this=0x2da1b10, e=0x7fffb82eb220) at /home/kde-devel/kde-qt/src/corelib/kernel/qobject.cpp:1081
#25 0x00007fbd6dffb856 in QApplicationPrivate::notify_helper (this=0x1d19c60, receiver=0x2da1b10, e=0x7fffb82eb220) at /home/kde-devel/kde-qt/src/gui/kernel/qapplication.cpp:4057
#26 0x00007fbd6dff99df in QApplication::notify (this=0x7fffb82eb730, receiver=0x2da1b10, e=0x7fffb82eb220) at /home/kde-devel/kde-qt/src/gui/kernel/qapplication.cpp:3604
#27 0x00007fbd72da74a7 in KApplication::notify (this=0x7fffb82eb730, receiver=0x2da1b10, event=0x7fffb82eb220) at /home/kde-devel/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#28 0x00007fbd6f651b7c in QCoreApplication::notifyInternal (this=0x7fffb82eb730, receiver=0x2da1b10, event=0x7fffb82eb220) at /home/kde-devel/kde-qt/src/corelib/kernel/qcoreapplication.cpp:610
#29 0x00007fbd6f655a35 in QCoreApplication::sendEvent (receiver=0x2da1b10, event=0x7fffb82eb220) at ../../include/QtCore/../../../kde-qt/src/corelib/kernel/qcoreapplication.h:213
#30 0x00007fbd6f68e115 in QTimerInfoList::activateTimers (this=0x1d1c8b0) at /home/kde-devel/kde-qt/src/corelib/kernel/qeventdispatcher_unix.cpp:572
#31 0x00007fbd6f689c4c in timerSourceDispatch (source=0x1d1c850) at /home/kde-devel/kde-qt/src/corelib/kernel/qeventdispatcher_glib.cpp:164
#32 0x00007fbd64016dbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#33 0x00007fbd6401a568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#34 0x00007fbd6401a690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#35 0x00007fbd6f68ad25 in QEventDispatcherGlib::processEvents (this=0x1d19820, flags={i = 36}) at /home/kde-devel/kde-qt/src/corelib/kernel/qeventdispatcher_glib.cpp:324
#36 0x00007fbd6e0ba85c in QGuiEventDispatcherGlib::processEvents (this=0x1d19820, flags={i = 36}) at /home/kde-devel/kde-qt/src/gui/kernel/qguieventdispatcher_glib.cpp:202
#37 0x00007fbd6f64edb8 in QEventLoop::processEvents (this=0x7fffb82eb570, flags={i = 36}) at /home/kde-devel/kde-qt/src/corelib/kernel/qeventloop.cpp:149
#38 0x00007fbd6f64eef5 in QEventLoop::exec (this=0x7fffb82eb570, flags={i = 0}) at /home/kde-devel/kde-qt/src/corelib/kernel/qeventloop.cpp:200
#39 0x00007fbd6f65227e in QCoreApplication::exec () at /home/kde-devel/kde-qt/src/corelib/kernel/qcoreapplication.cpp:888
#40 0x00007fbd6dff9626 in QApplication::exec () at /home/kde-devel/kde-qt/src/gui/kernel/qapplication.cpp:3526
#41 0x0000000000403783 in main (argc=3, argv=0x7fffb82eb8c8) at /home/kde-devel/src/KDE/kdepim/kmail/main.cpp:146

My first impression from the backtrace and the code is that maybe the FolderJob is being deleted without being unregistered from KMAcctImap.

Perhaps the problem is that in KMAcctImap::ignoreJobsForMessage, when a job is killed, it is removed from the list that is being iterated over.  From the QList::const_iterator docs:

"be aware that any non-const function call performed on the QList will render all existing iterators undefined"

*** Bug 198503 has been marked as a duplicate of this bug. ***

*** Bug 200406 has been marked as a duplicate of this bug. ***

Still happening in 4.3 rc2, witha different backtrace though:

Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  KMail::FolderJob::msgList (this=0x7f4bbf35c010) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f4bc1fe8005 in KMAcctImap::ignoreJobsForMessage (this=0x1d71d90, msg=0x34cdd80) at /build/buildd/kdepim-4.2.96/kmail/kmacctimap.cpp:215
#7  0x00007f4bc21065af in KMMoveCommand::execute (this=0x3178b90) at /build/buildd/kdepim-4.2.96/kmail/kmcommands.cpp:2084
#8  0x00007f4bc20ec362 in KMCommand::slotPostTransfer (this=0x3178b90, result=KMCommand::OK) at /build/buildd/kdepim-4.2.96/kmail/kmcommands.cpp:273
#9  0x00007f4bc20f606e in KMCommand::qt_metacall (this=0x3178b90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcb3d6a70)
    at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/kmcommands.moc:87
#10 0x00007f4bc2108265 in KMMoveCommand::qt_metacall (this=0x7fffcb3d6620, _c=3207970832, _id=55242304, _a=0x37a7fa0) at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#11 0x00007f4bbe1ff1f2 in QMetaObject::activate (sender=0x3178b90, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x37a7fa0) at kernel/qobject.cpp:3069
#12 0x00007f4bc20e958e in KMCommand::messagesTransfered (this=0x7fffcb3d6620, _t1=KMCommand::OK) at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/kmcommands.moc:102
#13 0x00007f4bc2104fe8 in KMCommand::transferSelectedMsgs (this=0x3178b90) at /build/buildd/kdepim-4.2.96/kmail/kmcommands.cpp:367
#14 0x00007f4bc2105216 in KMCommand::slotStart (this=0x3178b90) at /build/buildd/kdepim-4.2.96/kmail/kmcommands.cpp:265
#15 0x00007f4bc20f6082 in KMCommand::qt_metacall (this=0x3178b90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcb3d6cd0)
    at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/kmcommands.moc:86
#16 0x00007f4bc2108265 in KMMoveCommand::qt_metacall (this=0x7fffcb3d6620, _c=3207970832, _id=55242304, _a=0x37a7fa0) at /build/buildd/kdepim-4.2.96/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#17 0x00007f4bbe1ff1f2 in QMetaObject::activate (sender=0x34e8160, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x37a7fa0) at kernel/qobject.cpp:3069
#18 0x00007f4bbe20452f in QSingleShotTimer::timerEvent (this=0x34e8160) at kernel/qtimer.cpp:298
#19 0x00007f4bbe1f94d3 in QObject::event (this=0x34e8160, e=0x7f4bbf35c010) at kernel/qobject.cpp:1082
#20 0x00007f4bbe92e78d in QApplicationPrivate::notify_helper (this=0x1a7a360, receiver=0x34e8160, e=0x7fffcb3d7390) at kernel/qapplication.cpp:4084
#21 0x00007f4bbe93697a in QApplication::notify (this=0x7fffcb3d77f0, receiver=0x34e8160, e=0x7fffcb3d7390) at kernel/qapplication.cpp:4049
#22 0x00007f4bc2dc063b in KApplication::notify (this=0x7fffcb3d77f0, receiver=0x34e8160, event=0x7fffcb3d7390) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302
#23 0x00007f4bbe1e975c in QCoreApplication::notifyInternal (this=0x7fffcb3d77f0, receiver=0x34e8160, event=0x7fffcb3d7390) at kernel/qcoreapplication.cpp:602
#24 0x00007f4bbe2167f6 in QTimerInfoList::activateTimers (this=0x1a7ca80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 0x00007f4bbe212f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#26 0x00007f4bb509c20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007f4bb509f8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007f4bb509fa7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007f4bbe212e6f in QEventDispatcherGlib::processEvents (this=0x1a466d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#30 0x00007f4bbe9c6bef in QGuiEventDispatcherGlib::processEvents (this=0x7fffcb3d6620, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f4bbe1e8002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -885164544}) at kernel/qeventloop.cpp:149
#32 0x00007f4bbe1e83cd in QEventLoop::exec (this=0x7fffcb3d7640, flags={i = -885164464}) at kernel/qeventloop.cpp:200
#33 0x00007f4bbe1ea694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#34 0x00000000004030db in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.96/kmail/main.cpp:146

*** Bug 198044 has been marked as a duplicate of this bug. ***

*** Bug 199700 has been marked as a duplicate of this bug. ***

I was able to reproduce this easily with older releases.

I've just been trying 4.3 RC3 and I can't get it to segfault.  Are others still having issues?  If not I want to close the OpenSUSE bug I opened about this.

Sorry, I had this just yesterday using 4.2.98. I opened the inbox on an IMAP account, typed a search term in the search bar, selected all the messages and then hit 'delete'. KMail crashed.

Jepp, it wasn't easy but I just managed to crash KMail 4.2.98 by randomly deleting mails from my Spam folder:

Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f64e377c023 in KMAcctImap::ignoreJobsForMessage (this=0x2485190, msg=0x402bca0) at /build/buildd/kdepim-4.2.98/kmail/kmacctimap.cpp:215
#6  0x00007f64e389a67f in KMMoveCommand::execute (this=0x37dec60) at /build/buildd/kdepim-4.2.98/kmail/kmcommands.cpp:2084
#7  0x00007f64e3880432 in KMCommand::slotPostTransfer (this=0x37dec60, result=KMCommand::OK) at /build/buildd/kdepim-4.2.98/kmail/kmcommands.cpp:273
#8  0x00007f64e388a13e in KMCommand::qt_metacall (this=0x37dec60, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffecb6a220)
    at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmcommands.moc:87
#9  0x00007f64e389c335 in KMMoveCommand::qt_metacall (this=0x7fffecb69dd0, _c=62713288, _id=61935232, _a=0x3acf340) at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#10 0x00007f64df9941f2 in QMetaObject::activate (sender=0x37dec60, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x3acf340) at kernel/qobject.cpp:3069
#11 0x00007f64e387d65e in KMCommand::messagesTransfered (this=0x7fffecb69dd0, _t1=KMCommand::OK) at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmcommands.moc:102
#12 0x00007f64e38990b8 in KMCommand::transferSelectedMsgs (this=0x37dec60) at /build/buildd/kdepim-4.2.98/kmail/kmcommands.cpp:367
#13 0x00007f64e38992e6 in KMCommand::slotStart (this=0x37dec60) at /build/buildd/kdepim-4.2.98/kmail/kmcommands.cpp:265
#14 0x00007f64e388a152 in KMCommand::qt_metacall (this=0x37dec60, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffecb6a480)
    at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmcommands.moc:86
#15 0x00007f64e389c335 in KMMoveCommand::qt_metacall (this=0x7fffecb69dd0, _c=62713288, _id=61935232, _a=0x3acf340) at /build/buildd/kdepim-4.2.98/obj-x86_64-linux-gnu/kmail/kmcommands.moc:1706
#16 0x00007f64df9941f2 in QMetaObject::activate (sender=0x3d2d6e0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x3acf340) at kernel/qobject.cpp:3069
#17 0x00007f64df99952f in QSingleShotTimer::timerEvent (this=0x3d2d6e0) at kernel/qtimer.cpp:298
#18 0x00007f64df98e4d3 in QObject::event (this=0x3d2d6e0, e=0x3bcedc8) at kernel/qobject.cpp:1082
#19 0x00007f64e00c378d in QApplicationPrivate::notify_helper (this=0x2162050, receiver=0x3d2d6e0, e=0x7fffecb6ab40) at kernel/qapplication.cpp:4084
#20 0x00007f64e00cb97a in QApplication::notify (this=0x7fffecb6afa0, receiver=0x3d2d6e0, e=0x7fffecb6ab40) at kernel/qapplication.cpp:4049
#21 0x00007f64e455571b in KApplication::notify (this=0x7fffecb6afa0, receiver=0x3d2d6e0, event=0x7fffecb6ab40) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#22 0x00007f64df97e75c in QCoreApplication::notifyInternal (this=0x7fffecb6afa0, receiver=0x3d2d6e0, event=0x7fffecb6ab40) at kernel/qcoreapplication.cpp:602
#23 0x00007f64df9ab7f6 in QTimerInfoList::activateTimers (this=0x2164ba0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 0x00007f64df9a7f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#25 0x00007f64d682b20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0x00007f64d682e8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0x00007f64d682ea7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0x00007f64df9a7e6f in QEventDispatcherGlib::processEvents (this=0x21256d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#29 0x00007f64e015bbef in QGuiEventDispatcherGlib::processEvents (this=0x7fffecb69dd0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x00007f64df97d002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -323572304}) at kernel/qeventloop.cpp:149
#31 0x00007f64df97d3cd in QEventLoop::exec (this=0x7fffecb6adf0, flags={i = -323572224}) at kernel/qeventloop.cpp:200
#32 0x00007f64df97f694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#33 0x00000000004030db in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-4.2.98/kmail/main.cpp:146

*** Bug 201825 has been marked as a duplicate of this bug. ***

I just subscribed to my gmail spam folder and deleted 475 emails.

I did not get a crash.  With previous versions I could get it to crash within 5 or 10 email deletions.

I was testing 4.2.98 (release 148) as compiled for Novell on their OBS for OpenSUSE 11.1

Yes, something has definitely changed to reduce the frequency with which this occurs, but it does still happen.

Created attachment 35739 [details]
Stack of the crash

*** Bug 201825 has been marked as a duplicate of this bug. ***

*** Bug 200022 has been marked as a duplicate of this bug. ***

Created attachment 35984 [details]
Usual crash while cleaning up my inbox

I actually got a kcrash this crash, so I'm attaching it in case it helps. I wasn't doing anything out of the ordinary. Just my usual inbox cleanup: moving emails from two imap accounts to my personal imap server

*** Bug 203105 has been marked as a duplicate of this bug. ***

*** Bug 203089 has been marked as a duplicate of this bug. ***

*** Bug 203361 has been marked as a duplicate of this bug. ***

My Bugreport (https://bugs.kde.org/show_bug.cgi?id=203089) has been marked as a duplicate and I guess noone ever read what I wrote there and so never tried it.

Copy n paste:

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 AFTER this little dialog appeared telling me whats
happening (downloading message x/139), KMail doesn't crash anymore when marking
spam/ham one by one.

*** Bug 203459 has been marked as a duplicate of this bug. ***

*** Bug 203914 has been marked as a duplicate of this bug. ***

Hm, I always read about crashes with IMAP folders, but here it actually happens with a POP account...
Using KDE 4.3 Kubuntu 9.04 Kontact 4.3.0. Just had a crash a few minutes ago, same backtrace as those above. It crashes with the regularity of a metronome: at least daily, sometimes more often, always when moving mails to other folders, be this manually or with a filter. The amount of files moved doesn't matter apparently, I had this when moving 300 and when moving 10.

*** Bug 205960 has been marked as a duplicate of this bug. ***

*** Bug 206040 has been marked as a duplicate of this bug. ***

*** Bug 206309 has been marked as a duplicate of this bug. ***

*** Bug 206726 has been marked as a duplicate of this bug. ***

*** Bug 206962 has been marked as a duplicate of this bug. ***

*** Bug 207235 has been marked as a duplicate of this bug. ***

*** Bug 207758 has been marked as a duplicate of this bug. ***

With a bit of luck, this problem could be fixed in KDE 4.3.2, a potential fix has been committed in r1024448, see http://websvn.kde.org/?revision=1024448&view=revision .

Bug 126999 is a dupe (well, the other way around, actually, but the action seems to go on here)

> Bug 126999 is a dupe 

No, the backtrace in the first comment is different. The backtraces starting with comment 8 don't belong to that bug report, they indeed look like this problem here. But the original report is different.

*** Bug 210120 has been marked as a duplicate of this bug. ***

*** Bug 210960 has been marked as a duplicate of this bug. ***

*** Bug 209629 has been marked as a duplicate of this bug. ***

*** Bug 211431 has been marked as a duplicate of this bug. ***

*** Bug 200644 has been marked as a duplicate of this bug. ***

*** Bug 211673 has been marked as a duplicate of this bug. ***

This always happens when deleting a new unread message that's being downloaded. I tend to push shift-delete on some of them and after confirming a deletion, the crash consistently occurs if the message preview has not yet loaded at that point.

*** Bug 211956 has been marked as a duplicate of this bug. ***

*** Bug 212303 has been marked as a duplicate of this bug. ***

*** Bug 212288 has been marked as a duplicate of this bug. ***

*** Bug 212510 has been marked as a duplicate of this bug. ***

*** Bug 212682 has been marked as a duplicate of this bug. ***

*** Bug 213901 has been marked as a duplicate of this bug. ***

*** Bug 213807 has been marked as a duplicate of this bug. ***

*** Bug 214189 has been marked as a duplicate of this bug. ***

*** Bug 214040 has been marked as a duplicate of this bug. ***

*** Bug 213944 has been marked as a duplicate of this bug. ***

*** Bug 214528 has been marked as a duplicate of this bug. ***

*** Bug 208815 has been marked as a duplicate of this bug. ***

*** Bug 209605 has been marked as a duplicate of this bug. ***

*** Bug 215416 has been marked as a duplicate of this bug. ***

*** Bug 215799 has been marked as a duplicate of this bug. ***

*** Bug 216775 has been marked as a duplicate of this bug. ***

*** Bug 217076 has been marked as a duplicate of this bug. ***

*** Bug 217249 has been marked as a duplicate of this bug. ***

*** Bug 217507 has been marked as a duplicate of this bug. ***

*** Bug 217999 has been marked as a duplicate of this bug. ***

*** Bug 217758 has been marked as a duplicate of this bug. ***

Application that crashed: kontact
Think this is more are less the same bug:

Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Deliting some message from my INBOX in a IMAP account (I think it still retrieved some more messages in the background while I was deleting the first ones)

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x680077) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x680077) at /usr/include/qt4/QtCore/qlist.h:111
#8  KMail::FolderJob::msgList (this=0x680077) at ../../kmail/folderjob.cpp:120
#9  0xb449682d in KMAcctImap::ignoreJobsForMessage (this=0x8f03638, msg=0xa48f7c0) at ../../kmail/kmacctimap.cpp:217
#10 0xb44adb83 in KMFolderImap::ignoreJobsForMessage (this=0x8be9120, msg=0xa48f7c0) at ../../kmail/kmfolderimap.cpp:1564
#11 0xb45ca2cc in KMMoveCommand::execute (this=0xa482c38) at ../../kmail/kmcommands.cpp:2095
#12 0xb45adf22 in KMCommand::slotPostTransfer (this=0xa482c38, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:274
#13 0xb45b861f in KMCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf812388) at ./kmcommands.moc:87
#14 0xb45cb56a in KMMoveCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf812388) at ./kmcommands.moc:1706
#15 0xb45cb632 in KMTrashMsgCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf812388) at ./kmcommands.moc:1758
#16 0x019e2263 in QMetaObject::activate (sender=0xa482c38, from_signal_index=4, to_signal_index=4, argv=0xbf812388) at kernel/qobject.cpp:3113
#17 0x019e2ec2 in QMetaObject::activate (sender=0xa482c38, m=0xb49e7634, local_signal_index=0, argv=0xbf812388) at kernel/qobject.cpp:3187
#18 0xb45aa093 in KMCommand::messagesTransfered (this=0xa482c38, _t1=KMCommand::OK) at ./kmcommands.moc:102
#19 0xb45c8496 in KMCommand::transferSelectedMsgs (this=0xa482c38) at ../../kmail/kmcommands.cpp:368
#20 0xb45c86e2 in KMCommand::slotStart (this=0xa482c38) at ../../kmail/kmcommands.cpp:266
#21 0xb45b85fb in KMCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf8125ac) at ./kmcommands.moc:86
#22 0xb45cb56a in KMMoveCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf8125ac) at ./kmcommands.moc:1706
#23 0xb45cb632 in KMTrashMsgCommand::qt_metacall (this=0xa482c38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf8125ac) at ./kmcommands.moc:1758
#24 0x019e2263 in QMetaObject::activate (sender=0x97bdf88, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x019e2ec2 in QMetaObject::activate (sender=0x97bdf88, m=0x1abc908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x019e7387 in QSingleShotTimer::timeout (this=0x97bdf88) at .moc/release-shared/qtimer.moc:76
#27 0x019e749c in QSingleShotTimer::timerEvent (this=0x97bdf88) at kernel/qtimer.cpp:298
#28 0x019dc3bf in QObject::event (this=0x97bdf88, e=0xbf812a40) at kernel/qobject.cpp:1075
#29 0x0100ff54 in QApplicationPrivate::notify_helper (this=0x861d730, receiver=0x97bdf88, e=0xbf812a40) at kernel/qapplication.cpp:4056
#30 0x0101767c in QApplication::notify (this=0xbf812da4, receiver=0x97bdf88, e=0xbf812a40) at kernel/qapplication.cpp:3603
#31 0x006b21aa in KApplication::notify (this=0xbf812da4, receiver=0x97bdf88, event=0xbf812a40) at ../../kdeui/kernel/kapplication.cpp:302
#32 0x019cc6cb in QCoreApplication::notifyInternal (this=0xbf812da4, receiver=0x97bdf88, event=0xbf812a40) at kernel/qcoreapplication.cpp:610
#33 0x019f97ce in QCoreApplication::sendEvent (this=0x860eb34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#34 QTimerInfoList::activateTimers (this=0x860eb34) at kernel/qeventdispatcher_unix.cpp:572
#35 0x019f70e0 in timerSourceDispatch (source=0x860eb00) at kernel/qeventdispatcher_glib.cpp:165
#36 0x02791e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#37 0x02795720 in ?? () from /lib/libglib-2.0.so.0
#38 0x02795853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#39 0x019f702c in QEventDispatcherGlib::processEvents (this=0x85ec9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#40 0x010b0be5 in QGuiEventDispatcherGlib::processEvents (this=0x85ec9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#41 0x019cac79 in QEventLoop::processEvents (this=0xbf812d04, flags=) at kernel/qeventloop.cpp:149
#42 0x019cb0ca in QEventLoop::exec (this=0xbf812d04, flags=...) at kernel/qeventloop.cpp:201
#43 0x019cd53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#44 0x0100fdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#45 0x0804b4e6 in main (argc=1, argv=0xbf812fc4) at ../../../kontact/src/main.cpp:218

On Friday 11 December 2009 01:35:26 Verena Ruff wrote:
> https://bugs.kde.org/show_bug.cgi?id=163071
> 
> 
> Verena Ruff <ve.ru@triosolutions.at> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |ve.ru@triosolutions.at
> 
> 
> 
> 
> --- Comment #109 from Verena Ruff <ve ru triosolutions at>  2009-12-11
>  08:35:05 --- Application that crashed: kontact
> Think this is more are less the same bug:

I agree. Actually, I don't know if KMail/Kontact was retrieving new messages 
but it might have the same cause.

Robin

> Version of the application: 4.3.4
> KDE Version: 4.3.4 (KDE 4.3.4)
> Qt Version: 4.5.2
> Operating System: Linux 2.6.31-16-generic i686
> Distribution: Ubuntu 9.10
> 
> What I was doing when the application crashed:
> Deliting some message from my INBOX in a IMAP account (I think it still
> retrieved some more messages in the background while I was deleting the
>  first ones)
> 
>  -- Backtrace:
[deleted]

*** Bug 218459 has been marked as a duplicate of this bug. ***

*** Bug 218647 has been marked as a duplicate of this bug. ***

From bug 218953:
---
What I was doing when the application crashed:
I was selecting emails for deletion from an IMAP folder and it
has crashed. The folder was using SSL and not TLS.

*** Bug 218953 has been marked as a duplicate of this bug. ***

*** Bug 219003 has been marked as a duplicate of this bug. ***

Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.27.41-170.2.117.fc10.x86_64 x86_64
Distribution: "Fedora release 10 (Cambridge)"

What I was doing when the application crashed:
It'll do it anytime I delete while a queue of deletes is still processing.  Current workaround (when I remember) is to make another selection, wait for it to display the currently selected message, when it gets to it, and then proceed with the delete.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QList () at /usr/include/QtCore/qlist.h:111
#6  KMail::FolderJob::msgList (this=0xff8a1b21ff642722) at /usr/src/debug/kdepim-4.3.3/kmail/folderjob.cpp:120
#7  0x0000003d72a84735 in KMAcctImap::ignoreJobsForMessage (this=0x198cb70, msg=0x5042330) at /usr/src/debug/kdepim-4.3.3/kmail/kmacctimap.cpp:215
#8  0x0000003d72ba3cd7 in KMMoveCommand::execute (this=0x2db1d40) at /usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:2096
#9  0x0000003d72b89372 in KMCommand::slotPostTransfer (this=0x2db1d40, result=KMCommand::OK) at /usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:275
#10 0x0000003d72b9336e in KMCommand::qt_metacall (this=0x2db1d40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7ad2b9d0)
    at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:87
#11 0x0000003d72ba5995 in KMMoveCommand::qt_metacall (this=0x7fff7ad2b580, _c=4284753698, _id=79546736, _a=0x568a270) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#12 0x0000003d8f358662 in QMetaObject::activate (sender=0x2db1d40, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x568a270) at kernel/qobject.cpp:3112
#13 0x0000003d72b8654e in KMCommand::messagesTransfered (this=0x7fff7ad2b580, _t1=KMCommand::OK) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:102
#14 0x0000003d72ba20c8 in KMCommand::transferSelectedMsgs (this=0x2db1d40) at /usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:369
#15 0x0000003d72ba22f6 in KMCommand::slotStart (this=0x2db1d40) at /usr/src/debug/kdepim-4.3.3/kmail/kmcommands.cpp:267
#16 0x0000003d72b93382 in KMCommand::qt_metacall (this=0x2db1d40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7ad2bc30)
    at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:86
#17 0x0000003d72ba5995 in KMMoveCommand::qt_metacall (this=0x7fff7ad2b580, _c=4284753698, _id=79546736, _a=0x568a270) at /usr/src/debug/kdepim-4.3.3/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#18 0x0000003d8f358662 in QMetaObject::activate (sender=0x2dc8010, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x568a270) at kernel/qobject.cpp:3112
#19 0x0000003d8f35e35f in QSingleShotTimer::timerEvent (this=0x2dc8010) at kernel/qtimer.cpp:298
#20 0x0000003d8f353473 in QObject::event (this=0x2dc8010, e=0xff8a1b21ff642722) at kernel/qobject.cpp:1074
#21 0x0000003d6919001d in QApplicationPrivate::notify_helper (this=0x699c70, receiver=0x2dc8010, e=0x7fff7ad2c2f0) at kernel/qapplication.cpp:4065
#22 0x0000003d6919825a in QApplication::notify (this=0x7fff7ad2c640, receiver=0x2dc8010, e=0x7fff7ad2c2f0) at kernel/qapplication.cpp:4030
#23 0x0000003d6b81351b in KApplication::notify (this=0x7fff7ad2c640, receiver=0x2dc8010, event=0x7fff7ad2c2f0) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#24 0x0000003d8f34378c in QCoreApplication::notifyInternal (this=0x7fff7ad2c640, receiver=0x2dc8010, event=0x7fff7ad2c2f0) at kernel/qcoreapplication.cpp:610
#25 0x0000003d8f370859 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (this=0x695190) at kernel/qeventdispatcher_unix.cpp:580
#27 0x0000003d8f36cd5d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#28 0x0000003099e377bb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#29 0x0000003099e3af8d in ?? () from /lib64/libglib-2.0.so.0
#30 0x0000003099e3b14b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#31 0x0000003d8f36ccbf in QEventDispatcherGlib::processEvents (this=0x66b0f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#32 0x0000003d6922753f in QGuiEventDispatcherGlib::processEvents (this=0x7fff7ad2b580, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#33 0x0000003d8f342022 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#34 0x0000003d8f3423f4 in QEventLoop::exec (this=0x7fff7ad2c5a0, flags=) at kernel/qeventloop.cpp:201
#35 0x0000003d8f3446c4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#36 0x00000000004045f5 in main (argc=1, argv=0x7fff7ad2cd28) at /usr/src/debug/kdepim-4.3.3/kontact/src/main.cpp:218

Can confirm bug on Gentoo Linux with KDE 4.3.4 and matching Kontact (KMail 1.12.2)

*** Bug 220687 has been marked as a duplicate of this bug. ***

*** Bug 221781 has been marked as a duplicate of this bug. ***

Created attachment 39878 [details]
New crash information added by DrKonqi

I select Inbox folder and quickly press "delete" on some new (unread) messages, and after succesfully delete 3-5 messages I got this crash.

*** Bug 224294 has been marked as a duplicate of this bug. ***

From bug 224423 (KDE SC 4.4RC2):
---

 -- Backtrace:
#5  QList (this=0x4e) at /usr/include/qt4/QtCore/qlist.h:114
#6  KMail::FolderJob::msgList (this=0x4e) at ../../kmail/folderjob.cpp:120
#7  0x0108083d in KMAcctImap::ignoreJobsForMessage (this=0x9c26670,
msg=0xbe78800) at ../../kmail/kmacctimap.cpp:217
#8  0x01096693 in KMFolderImap::ignoreJobsForMessage (this=0x908b8a0,
msg=0xbe78800) at ../../kmail/kmfolderimap.cpp:1555
#9  0x011a8a9c in KMMoveCommand::execute (this=0xb2a5af0) at
../../kmail/kmcommands.cpp:2185
#10 0x01199392 in KMCommand::slotPostTransfer (this=0xb2a5af0,
result=KMCommand::OK) at ../../kmail/kmcommands.cpp:291
#11 0x011a341f in KMCommand::qt_metacall (this=0xb2a5af0,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfc6a428) at ./kmcommands.moc:93
#12 0x011a389a in KMMoveCommand::qt_metacall (this=0xb2a5af0,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfc6a428) at
./kmcommands.moc:1971

*** Bug 224423 has been marked as a duplicate of this bug. ***

*** Bug 224218 has been marked as a duplicate of this bug. ***

*** Bug 224159 has been marked as a duplicate of this bug. ***

*** Bug 222371 has been marked as a duplicate of this bug. ***

*** Bug 220600 has been marked as a duplicate of this bug. ***

*** Bug 224699 has been marked as a duplicate of this bug. ***

I'd like to note that I have upgraded to 4.4rc2 on openSUSE and I cannot trigger this bug, where before it was not difficult to provoke. The only change from default is that neopmuk is disabled, but the 4.4 version is faster and more repsonive to my large IMAP mail store even over a slow net connection... Nice work.

Created attachment 41097 [details]
New crash information added by DrKonqi

I've forwarded a bunch of mails, shift-deleted them and then moved two remaining (not forwarded) mails to another folder.
KMail then crashed.

Created attachment 42255 [details]
New crash information added by DrKonqi

This happens to me, when i delete more than one mail via the 'delete mail' button quickly. Perhaps there is a problem, because the delete was not send to the imap-server.

*** Bug 225950 has been marked as a duplicate of this bug. ***

*** Bug 222182 has been marked as a duplicate of this bug. ***

*** Bug 229376 has been marked as a duplicate of this bug. ***

*** Bug 229345 has been marked as a duplicate of this bug. ***

*** Bug 221652 has been marked as a duplicate of this bug. ***

*** Bug 224873 has been marked as a duplicate of this bug. ***

*** Bug 229236 has been marked as a duplicate of this bug. ***

*** Bug 231225 has been marked as a duplicate of this bug. ***

Created attachment 42769 [details]
New crash information added by DrKonqi

This happens fairly consistently when using Spam Controls with the target folder on the IMAP server instead of in Local Folders.

*** Bug 234577 has been marked as a duplicate of this bug. ***

*** Bug 226415 has been marked as a duplicate of this bug. ***

Created attachment 42989 [details]
backtrace 

Same bug of the first post. I think kmail has a problem with incomplete messages. I downloaded the email header with imap. If I don't wait the download of the full mail to complete and delete it or ask to open an attachment then kmail crashes. This should not be an issue, the client should wait and proceed with the requested action when possible. In my humble opinion kmail is trying to access a message that's not yet in the hard disk, memory access violation.

Created attachment 43051 [details]
New crash information added by DrKonqi

This happens in KMail whenever I quickly delete several messages in a row, deleting one, I think, before the previously deleted message has actualy been sent to the trash.

Created attachment 43315 [details]
New crash information added by DrKonqi

As reported by everyone else here, this happens when deleting messages from an IMAP account quickly.

*** Bug 238435 has been marked as a duplicate of this bug. ***

*** Bug 237638 has been marked as a duplicate of this bug. ***

*** Bug 238464 has been marked as a duplicate of this bug. ***

*** Bug 238414 has been marked as a duplicate of this bug. ***

*** Bug 238281 has been marked as a duplicate of this bug. ***

*** Bug 238720 has been marked as a duplicate of this bug. ***

*** Bug 237063 has been marked as a duplicate of this bug. ***

*** Bug 236537 has been marked as a duplicate of this bug. ***

*** Bug 235831 has been marked as a duplicate of this bug. ***

*** Bug 239039 has been marked as a duplicate of this bug. ***

*** Bug 240193 has been marked as a duplicate of this bug. ***

Created attachment 48089 [details]
New crash information added by DrKonqi

I was deleting a lot of mails in my inbox on imap.gmail.com, so they were moved to the deleted mail folder on the imap server.

*** Bug 241940 has been marked as a duplicate of this bug. ***

*** Bug 242143 has been marked as a duplicate of this bug. ***

*** Bug 242494 has been marked as a duplicate of this bug. ***

*** Bug 243282 has been marked as a duplicate of this bug. ***

*** Bug 243750 has been marked as a duplicate of this bug. ***

Created attachment 49651 [details]
New crash information added by DrKonqi

I was deleting mails from the IMAP folder when it has crashed. No more
information I can give.

*** Bug 246817 has been marked as a duplicate of this bug. ***

*** Bug 126999 has been marked as a duplicate of this bug. ***

*** Bug 246334 has been marked as a duplicate of this bug. ***

*** Bug 247496 has been marked as a duplicate of this bug. ***

*** Bug 246112 has been marked as a duplicate of this bug. ***

*** Bug 246069 has been marked as a duplicate of this bug. ***

*** Bug 244057 has been marked as a duplicate of this bug. ***

*** Bug 247512 has been marked as a duplicate of this bug. ***

I have the same bug in KDE 4.5. Kmail 1.13.3. It seems to me it's time to fix, no?

Hi,

wait for kMail 2.0 which was supposed to be in 4.5, but is currently postponed till 4.5.1.
This is the akonadi version, so complete new infrastructure.
So exactly this can not happen any more, but of course there will be other new bugs, maybe as well some crashes if you delete too many mails-)

12.08.2010, 22:32, "Achim Schaefer" <achim_schaefer@gmx.de>:
> https://bugs.kde.org/show_bug.cgi?id=163071
>
> --- Comment #173 from Achim Schaefer <achim_schaefer gmx de> 2010-08-12 20:32:01 ---
> Hi,
>
> wait for kMail 2.0 which was supposed to be in 4.5, but is currently postponed
> till 4.5.1.
> This is the akonadi version, so complete new infrastructure.
> So exactly this can not happen any more, but of course there will be other new
> bugs, maybe as well some crashes if you delete too many mails-)
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.



Thank you, sir!

Created attachment 50113 [details]
New crash information added by DrKonqi

kontact (4.4.5) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.7.0

- What I was doing when the application crashed:
* subscribe an IMAP account
* fetch all headers
* apply a "by new" filter
* delete one of above filtered messages.

-- Backtrace (Reduced):
#7  QList (this=0x45ea) at /usr/include/qt4/QtCore/qlist.h:118
#8  KMail::FolderJob::msgList (this=0x45ea) at ../../kmail/folderjob.cpp:120
#9  0xae48c0cd in KMAcctImap::ignoreJobsForMessage (this=0xa10d320, msg=0xad56400) at ../../kmail/kmacctimap.cpp:217
#10 0xae4a24b3 in KMFolderImap::ignoreJobsForMessage (this=0xa116be0, msg=0xad56400) at ../../kmail/kmfolderimap.cpp:1560
#11 0xae5b80ac in KMMoveCommand::execute (this=0xadf4e70) at ../../kmail/kmcommands.cpp:2200

With KDE 4.5 and KDEPIM 4.4 (both current branches) I can offer:

[KCrash Handler]
#6  0x00007fd475f86db0 in begin (this=0x2e2b620, msg=0x506f380) at /D/build/kde4/stable/kdepim/kmail/kmacctimap.moc:102
#7  begin (this=0x2e2b620, msg=0x506f380) at /D/src/kde4/qt/include/QtCore/../../src/corelib/tools/qlist.h:248
#8  first (this=0x2e2b620, msg=0x506f380) at /D/src/kde4/qt/include/QtCore/../../src/corelib/tools/qlist.h:263
#9  KMAcctImap::ignoreJobsForMessage (this=0x2e2b620, msg=0x506f380) at /D/src/kde4/stable/kdepim/kmail/kmacctimap.cpp:217
#10 0x00007fd476089de4 in KMMoveCommand::execute (this=0x5276ed0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:2208
#11 0x00007fd47607c355 in KMCommand::slotPostTransfer (this=0x5276ed0, result=KMCommand::OK) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:295
#12 0x00007fd47608566f in KMCommand::qt_metacall (this=0x5276ed0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbd1a4ea0) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:93
#13 0x00007fd476085843 in KMMoveCommand::qt_metacall (this=0x3b1de1168, _c=261816, _id=1970436262, _a=0x7fd4) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:1971
#14 0x00007fd48527ef82 in QMetaObject::activate (sender=0x5276ed0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fd4) at kernel/qobject.cpp:3287
#15 0x00007fd4760781ac in KMCommand::messagesTransfered (this=0x3b1de1168, _t1=KMCommand::OK) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:108
#16 0x00007fd47608c6db in KMCommand::transferSelectedMsgs (this=0x5276ed0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:393
#17 0x00007fd47608c8ca in KMCommand::slotStart (this=0x5276ed0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:287

*** Bug 249666 has been marked as a duplicate of this bug. ***

*** Bug 252558 has been marked as a duplicate of this bug. ***

*** Bug 254069 has been marked as a duplicate of this bug. ***

*** Bug 252678 has been marked as a duplicate of this bug. ***

Created attachment 52741 [details]
New crash information added by DrKonqi

KMail crashed while I was organizing my mails into DIMAP folders. I was using the filter bar to filter mails, mark all, move them to a folder. Then I moved to the next folder, filtered, moved mails. Then I stayed in that folder, filtered for another keyword, and moved these mails to the same folder as last time. System started to choke (slow interactive performance, harddisk thrashing), then KMail crashed.

Created attachment 52742 [details]
New crash information added by DrKonqi

KMail crashed while I was organizing my mails into DIMAP folders. I was using the filter bar to filter mails, mark all, move them to a folder. Then I moved to the next folder, filtered, moved mails. Then I stayed in that folder, filtered for another keyword, and moved these mails to the same folder as last time. System started to choke (slow interactive performance, harddisk thrashing), then KMail crashed.

Created attachment 52997 [details]
New crash information added by DrKonqi

kmail (1.13.5) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

The same error. Nothin else

-- Backtrace (Reduced):
#7  ref (this=0xa10fe90) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#8  QList (this=0xa10fe90) at /usr/include/qt4/QtCore/qlist.h:118
#9  KMail::FolderJob::msgList (this=0xa10fe90) at ../../kmail/folderjob.cpp:120
#10 0x0120181d in KMAcctImap::ignoreJobsForMessage (this=0x9ae5d88, msg=0xa3840d0) at ../../kmail/kmacctimap.cpp:217
#11 0x012180d3 in KMFolderImap::ignoreJobsForMessage (this=0x9a7ae88, msg=0xa3840d0) at ../../kmail/kmfolderimap.cpp:1560

Created attachment 53122 [details]
New crash information added by DrKonqi

Try do delete a new unreaded message on an imap server.

[Comment from a bug triager]
According to bug 256136, a similar crash should be fixed in kdepim 4.4.7. I asked the developers to check if this specific crash could also be fixed.

*** Bug 249381 has been marked as a duplicate of this bug. ***

*** Bug 254962 has been marked as a duplicate of this bug. ***

*** Bug 256992 has been marked as a duplicate of this bug. ***

*** Bug 256678 has been marked as a duplicate of this bug. ***

(In reply to comment #185)
> [Comment from a bug triager]
> According to bug 256136, a similar crash should be fixed in kdepim 4.4.7. I
> asked the developers to check if this specific crash could also be fixed.

Not really :-( I still get this crash:

#6  QList (this=0x20000a007b0020) at /D/src/kde4/qt/include/QtCore/../../src/corelib/tools/qlist.h:118
#7  KMail::FolderJob::msgList (this=0x20000a007b0020) at /D/src/kde4/stable/kdepim/kmail/folderjob.cpp:120
#8  0x00007f2d82ab119f in KMAcctImap::ignoreJobsForMessage (this=0x23fff50, msg=0x4cb40f0) at /D/src/kde4/stable/kdepim/kmail/kmacctimap.cpp:217
#9  0x00007f2d82ba6240 in KMMoveCommand::execute (this=0x468fdc0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:2208
#10 0x00007f2d82b9ae84 in KMCommand::slotPostTransfer (this=0x468fdc0, result=KMCommand::OK) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:295
#11 0x00007f2d82ba215d in KMCommand::qt_metacall (this=0x468fdc0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa632d1a0) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:93
#12 0x00007f2d82ba5b93 in KMMoveCommand::qt_metacall (this=0x468fdc0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa632d1a0) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:1971
#13 0x00007f2d91c4d4ef in QMetaObject::activate (sender=0x468fdc0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffa632d1a0) at kernel/qobject.cpp:3278
#14 0x00007f2d82b932e0 in KMCommand::messagesTransfered (this=<value optimized out>, _t1=KMCommand::OK) at /D/build/kde4/stable/kdepim/kmail/kmcommands.moc:108
#15 0x00007f2d82b9aac5 in KMCommand::transferSelectedMsgs (this=0x468fdc0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:393
#16 0x00007f2d82b9acbc in KMCommand::slotStart (this=0x468fdc0) at /D/src/kde4/stable/kdepim/kmail/kmcommands.cpp:287

*** Bug 257998 has been marked as a duplicate of this bug. ***

*** Bug 258950 has been marked as a duplicate of this bug. ***

Created attachment 55523 [details]
New crash information added by DrKonqi

kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:
Deleting Mails from an IMAP email-account in KMail

-- Backtrace (Reduced):
#6  ref (this=0x2f55100) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#7  QList (this=0x2f55100) at /usr/include/qt4/QtCore/qlist.h:118
#8  KMail::FolderJob::msgList (this=0x2f55100) at ../../kmail/folderjob.cpp:120
#9  0x00007f319b126df3 in KMAcctImap::ignoreJobsForMessage (this=0x2187af0, msg=0x2ef3df0) at ../../kmail/kmacctimap.cpp:217
#10 0x00007f319b23d627 in KMMoveCommand::execute (this=0x2c67a70) at ../../kmail/kmcommands.cpp:2208

Created attachment 55649 [details]
New crash information added by DrKonqi

kontact (4.4.9) on KDE Platform 4.5.4 (KDE 4.5.4) using Qt 4.7.0

- What I was doing when the application crashed:
I also still have this type of crash
I got it when using delete key very quickly on mails from an imap folder

-- Backtrace (Reduced):
#6  QList (this=0x50) at /usr/include/qt4/QtCore/qlist.h:118
#7  KMail::FolderJob::msgList (this=0x50) at ../../kmail/folderjob.cpp:120
#8  0x00007f93fb601b9a in KMAcctImap::ignoreJobsForMessage (this=0x153dd90, msg=<value optimized out>) at ../../kmail/kmacctimap.cpp:217
#9  0x00007f93fb7178e7 in KMMoveCommand::execute (this=0x41210d0) at ../../kmail/kmcommands.cpp:2208
#10 0x00007f93fb70693a in KMCommand::slotPostTransfer (this=0x41210d0, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:295

*** Bug 262442 has been marked as a duplicate of this bug. ***

*** Bug 263924 has been marked as a duplicate of this bug. ***

Created attachment 56651 [details]
New crash information added by DrKonqi

kontact (4.4.9) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1

- What I was doing when the application crashed:
I deleted a little fast multiple mails from imap account incoming folder

-- Backtrace (Reduced):
#7  ref (this=0x9f74680) at /usr/lib/qt4/include/QtCore/qatomic_i386.h:120
#8  QList (this=0x9f74680) at /usr/lib/qt4/include/QtCore/qlist.h:118
#9  KMail::FolderJob::msgList (this=0x9f74680) at /usr/src/debug/kdepim-4.4.9/kmail/folderjob.cpp:120
#10 0xab203a60 in KMAcctImap::ignoreJobsForMessage (this=0xa289a40, msg=0x9588150) at /usr/src/debug/kdepim-4.4.9/kmail/kmacctimap.cpp:217
#11 0xab21a933 in KMFolderImap::ignoreJobsForMessage (this=0x99cd590, msg=0x9588150) at /usr/src/debug/kdepim-4.4.9/kmail/kmfolderimap.cpp:1560

*** Bug 265639 has been marked as a duplicate of this bug. ***

*** Bug 264191 has been marked as a duplicate of this bug. ***

*** Bug 262472 has been marked as a duplicate of this bug. ***

*** Bug 262334 has been marked as a duplicate of this bug. ***

*** Bug 237366 has been marked as a duplicate of this bug. ***

*** Bug 231297 has been marked as a duplicate of this bug. ***

*** Bug 264828 has been marked as a duplicate of this bug. ***

Created attachment 57380 [details]
New crash information added by DrKonqi

kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

I was browding my inbox. Every time I reach a specific email, it crashes kmail. I tried avoiding showing this email by selecting another email, and then ctrl+click on the problematic email (I wanted to delete the messages). Unfortunately, even if not viewed, the offending ctrl+clicking email crashes kmail as well.

-- Backtrace (Reduced):
#6  KHTMLPart::findFrameParent (this=0x0, callingPart=0x0, f=..., childFrame=0x7ffff272d2b8) at ../../khtml/khtml_part.cpp:5185
#7  0x00007ffa4758a835 in KHTMLPart::findFrame (this=0x0, f=...) at ../../khtml/khtml_part.cpp:5215
#8  0x00007ffa47672176 in DOM::HTMLFrameElementImpl::ensureUniqueName (this=0x2b7c280) at ../../khtml/html/html_baseimpl.cpp:277
#9  0x00007ffa47672923 in DOM::HTMLIFrameElementImpl::parseAttribute (this=0x2b7c280, attr=0x2b7c120) at ../../khtml/html/html_baseimpl.cpp:748
#10 0x00007ffa4761b8d5 in DOM::ElementImpl::setAttributeMap (this=0x2b7c290, list=<value optimized out>) at ../../khtml/xml/dom_elementimpl.cpp:586

*** Bug 267501 has been marked as a duplicate of this bug. ***

*** Bug 270485 has been marked as a duplicate of this bug. ***

*** Bug 270832 has been marked as a duplicate of this bug. ***

*** Bug 269534 has been marked as a duplicate of this bug. ***

*** Bug 267983 has been marked as a duplicate of this bug. ***

The crash cannot be reproduced in KMail2. The fix will be in kdepim 4.6

cleaning the CC list.

*** Bug 267372 has been marked as a duplicate of this bug. ***

*** Bug 272898 has been marked as a duplicate of this bug. ***

*** Bug 273662 has been marked as a duplicate of this bug. ***

*** Bug 274028 has been marked as a duplicate of this bug. ***

*** Bug 274450 has been marked as a duplicate of this bug. ***

*** Bug 275453 has been marked as a duplicate of this bug. ***

*** Bug 276284 has been marked as a duplicate of this bug. ***

*** Bug 277355 has been marked as a duplicate of this bug. ***

Clearing the CC list. The issue is fixed in kdepim > 4.6

*** Bug 277529 has been marked as a duplicate of this bug. ***

*** Bug 278585 has been marked as a duplicate of this bug. ***

*** Bug 280831 has been marked as a duplicate of this bug. ***

*** Bug 280610 has been marked as a duplicate of this bug. ***

*** Bug 256136 has been marked as a duplicate of this bug. ***

*** Bug 283069 has been marked as a duplicate of this bug. ***

*** Bug 282087 has been marked as a duplicate of this bug. ***

*** Bug 283645 has been marked as a duplicate of this bug. ***

Created attachment 71780 [details]
New crash information added by DrKonqi

kontact (4.4.10) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.2

- What I was doing when the application crashed: Reporting emails as spam crashes contact and thus kmail

-- Backtrace (Reduced):
#7  ref (this=0xa6b0768) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#8  QList (this=0xa6b0768) at /usr/include/qt4/QtCore/qlist.h:118
#9  KMail::FolderJob::msgList (this=0xa6b0768) at ../../kmail/folderjob.cpp:120
#10 0xb3407466 in KMAcctImap::ignoreJobsForMessage (this=0x93faaa0, msg=0x9ef6b78) at ../../kmail/kmacctimap.cpp:217
#11 0xb3419973 in KMFolderImap::ignoreJobsForMessage (this=0x940fcd0, msg=0x9ef6b78) at ../../kmail/kmfolderimap.cpp:1560