Bug 214040

Summary: Kontact/kmail Crashes while moving selected group of email from inbox to another imap folder on gmail
Product: [Applications] kontact Reporter: Elric Wolfsbruder <elric>
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 Elric Wolfsbruder 2009-11-10 22:15:27 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-gentoo-r5 x86_64

What I was doing when the application crashed:
1) launch kontact
2) Select kmail component
3) Expand gmail based account
4) select INBOX in said gmail based acct
5) using the Search / Filter field, filter the inbox to a slight smaller subset
6) Select all mail matching query with ctrl-A
7) Right click in the mail subject pain and select move to <some imap folder> within that gmail based account
8) Wait while kontact / kmail chugs through moving email.

Expected Result:  All select email will move to chose imap folder

Actual result: "Kontact has unexpectedly crashed"  before all mail is moved.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMail::FolderJob::msgList (this=0x8dad5e0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#6  0x00007f4960eecc24 in KMAcctImap::ignoreJobsForMessage (this=0x2b39310, msg=0x8b35d30) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1/kmail/kmacctimap.cpp:215
#7  0x00007f49610078ef in KMMoveCommand::execute (this=0x403f680) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1/kmail/kmcommands.cpp:2090
#8  0x00007f4960fed602 in KMCommand::slotPostTransfer (this=0x403f680, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1/kmail/kmcommands.cpp:274
#9  0x00007f4960ff73a6 in KMCommand::qt_metacall (this=0x403f680, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffefcd6b20)
    at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1_build/kmail/kmcommands.moc:87
#10 0x00007f49610094c5 in KMMoveCommand::qt_metacall (this=0x7fffefcd66c0, _c=148559328, _id=144691552, _a=0xee7ac50)
    at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1_build/kmail/kmcommands.moc:1706
#11 0x00007f4973243826 in QMetaObject::activate (sender=0x403f680, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xee7ac50) at kernel/qobject.cpp:3101
#12 0x00007f4960fea8ce in KMCommand::messagesTransfered (this=0x7fffefcd66c0, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1_build/kmail/kmcommands.moc:102
#13 0x00007f4961005d18 in KMCommand::transferSelectedMsgs (this=0x403f680) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1/kmail/kmcommands.cpp:368
#14 0x00007f4961005f36 in KMCommand::slotStart (this=0x403f680) at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1/kmail/kmcommands.cpp:266
#15 0x00007f4960ff73ba in KMCommand::qt_metacall (this=0x403f680, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffefcd6d90)
    at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1_build/kmail/kmcommands.moc:86
#16 0x00007f49610094c5 in KMMoveCommand::qt_metacall (this=0x7fffefcd66c0, _c=148559328, _id=144691552, _a=0xee7ac50)
    at /var/tmp/portage/kde-base/kmail-4.3.1-r1/work/kmail-4.3.1_build/kmail/kmcommands.moc:1706
#17 0x00007f4973243826 in QMetaObject::activate (sender=0x5187220, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xee7ac50) at kernel/qobject.cpp:3101
#18 0x00007f4973249baf in QSingleShotTimer::timerEvent (this=0x5187220) at kernel/qtimer.cpp:298
#19 0x00007f4973240153 in QObject::event (this=0x5187220, e=0x8dad5e0) at kernel/qobject.cpp:1066
#20 0x00007f4973fec8fd in QApplicationPrivate::notify_helper (this=0x235f130, receiver=0x5187220, e=0x7fffefcd7450) at kernel/qapplication.cpp:4065
#21 0x00007f4973ff41ba in QApplication::notify (this=0x7fffefcd78a0, receiver=0x5187220, e=0x7fffefcd7450) at kernel/qapplication.cpp:4030
#22 0x00007f4974d84f1b in KApplication::notify (this=0x7fffefcd78a0, receiver=0x5187220, event=0x7fffefcd7450)
    at /var/tmp/portage/kde-base/kdelibs-4.3.1-r2/work/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#23 0x00007f4973231a5b in QCoreApplication::notifyInternal (this=0x7fffefcd78a0, receiver=0x5187220, event=0x7fffefcd7450) at kernel/qcoreapplication.cpp:606
#24 0x00007f4973259656 in QTimerInfoList::activateTimers (this=0x2351a00) at kernel/qcoreapplication.h:213
#25 0x00007f49732564fd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#26 0x00007f496e5f84a9 in IA__g_main_context_dispatch (context=0x2351520) at gmain.c:1824
#27 0x00007f496e5fbae8 in g_main_context_iterate (context=0x2351520, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2455
#28 0x00007f496e5fbc9c in IA__g_main_context_iteration (context=0x2351520, may_block=1) at gmain.c:2518
#29 0x00007f497325645f in QEventDispatcherGlib::processEvents (this=0x2327990, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#30 0x00007f497407189f in QGuiEventDispatcherGlib::processEvents (this=0x7fffefcd66c0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#31 0x00007f4973230442 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -271747392}) at kernel/qeventloop.cpp:149
#32 0x00007f49732305dc in QEventLoop::exec (this=0x7fffefcd7700, flags={i = -271747312}) at kernel/qeventloop.cpp:197
#33 0x00007f497323261c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0x0000000000404b49 in main (argc=1, argv=0x7fffefcd7e78) at /var/tmp/portage/kde-base/kontact-4.3.1/work/kontact-4.3.1/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-11 01:12:21 UTC
Good testcase. Is it reproducible all the times ?
The backtrace looks related to some other reported bugs like bug 163071.
Thanks
Comment 2 Elric Wolfsbruder 2009-11-11 02:13:10 UTC
Unfortunately no.  I can not get i to repro all the time.  It has crashed 3 out of 7 times doing this however.
Comment 3 Christophe Marin 2009-11-12 23:33:36 UTC

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