Bug 224873

Summary: Kdepim KMail: Segmetation fault when moving messages between folders
Product: [Applications] kontact Reporter: ra.be.baerlin
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 ra.be.baerlin 2010-01-30 15:19:00 UTC
Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.30.10-105.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
KMail crashed often in accessing IMAP folders and when movnig messages.
It is a "new" behaviour after the update before the most recent.
Never happened the other 10 years I have been using Linux form Fedora 5 on.

uname -a: Linux vulture.xyz.org 2.6.30.10-105.fc11.x86_64 #1 SMP Thu Dec 24 16:41:51 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux

Kdepim: rpm -q kdepim --> kdepim-4.3.4-2.fc11.x86_64

Linux box is running on a AMD Athlon(tm) 64 X2 Dual Core Processor 6000+-machine with 4GB-RAM.




 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QList (l=<value optimized out>, this=<value optimized out>) at /usr/include/QtCore/qlist.h:111
#6  KMail::FolderJob::msgList (l=<value optimized out>, this=<value optimized out>) at /usr/src/debug/kdepim-4.3.4/kmail/folderjob.cpp:120
#7  0x00007f4a94cb4213 in KMAcctImap::ignoreJobsForMessage (this=0x1fc7f40, msg=0x4ad2d80) at /usr/src/debug/kdepim-4.3.4/kmail/kmacctimap.cpp:217
#8  0x00007f4a94dcd7d7 in KMMoveCommand::execute (this=0x58fa7c0) at /usr/src/debug/kdepim-4.3.4/kmail/kmcommands.cpp:2096
#9  0x00007f4a94db2ada in KMCommand::slotPostTransfer (this=0x58fa7c0, result=KMCommand::OK) at /usr/src/debug/kdepim-4.3.4/kmail/kmcommands.cpp:275
#10 0x00007f4a94dbcc33 in KMCommand::qt_metacall (this=0x58fa7c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff54b99790)
    at /usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:87
#11 0x00007f4a94dce8e0 in KMMoveCommand::qt_metacall (this=0x7fff54b99320, _c=49, _id=3, _a=0x7f4aae905eb8) at /usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#12 0x00007f4ab0512dcc in QMetaObject::activate (sender=0x58fa7c0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7f4aae905eb8) at kernel/qobject.cpp:3112
#13 0x00007f4a94dafc5e in KMCommand::messagesTransfered (this=0x7fff54b99320, _t1=KMCommand::OK) at /usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:102
#14 0x00007f4a94dcbafc in KMCommand::transferSelectedMsgs (this=0x58fa7c0) at /usr/src/debug/kdepim-4.3.4/kmail/kmcommands.cpp:369
#15 0x00007f4a94dcbd2f in KMCommand::slotStart (this=0x58fa7c0) at /usr/src/debug/kdepim-4.3.4/kmail/kmcommands.cpp:267
#16 0x00007f4a94dbcc16 in KMCommand::qt_metacall (this=0x58fa7c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff54b999f0)
    at /usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:86
#17 0x00007f4a94dce8e0 in KMMoveCommand::qt_metacall (this=0x7fff54b99320, _c=49, _id=3, _a=0x7f4aae905eb8) at /usr/src/debug/kdepim-4.3.4/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:1706
#18 0x00007f4ab0512dcc in QMetaObject::activate (sender=0x3835cf0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7f4aae905eb8) at kernel/qobject.cpp:3112
#19 0x00007f4ab0517daf in QSingleShotTimer::timerEvent (this=0x3835cf0) at kernel/qtimer.cpp:298
#20 0x00007f4ab050cdce in QObject::event (this=0x3835cf0, e=0x31) at kernel/qobject.cpp:1074
#21 0x00007f4aaf24063c in QApplicationPrivate::notify_helper (this=0x185bc50, receiver=0x3835cf0, e=0x7fff54b9a000) at kernel/qapplication.cpp:4065
#22 0x00007f4aaf24789e in QApplication::notify (this=0x7fff54b9a360, receiver=0x3835cf0, e=0x7fff54b9a000) at kernel/qapplication.cpp:4030
#23 0x00007f4ab1349bd6 in KApplication::notify (this=0x7fff54b9a360, receiver=0x3835cf0, event=0x7fff54b9a000) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#24 0x00007f4ab04fdbac in QCoreApplication::notifyInternal (this=0x7fff54b9a360, receiver=0x3835cf0, event=0x7fff54b9a000) at kernel/qcoreapplication.cpp:610
#25 0x00007f4ab05285d2 in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:580
#27 0x00007f4ab0525fed in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#28 0x00007f4aa913090e in g_main_dispatch (context=<value optimized out>) at gmain.c:1824
#29 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377
#30 0x00007f4aa91340e8 in g_main_context_iterate (context=0x185ca10, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455
#31 0x00007f4aa913420a in IA__g_main_context_iteration (context=0x185ca10, may_block=1) at gmain.c:2518
#32 0x00007f4ab0525f36 in QEventDispatcherGlib::processEvents (this=0x181d530, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#33 0x00007f4aaf2d302e in QGuiEventDispatcherGlib::processEvents (this=0x7fff54b99320, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00007f4ab04fc4b2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 36}) at kernel/qeventloop.cpp:149
#35 0x00007f4ab04fc884 in QEventLoop::exec (this=0x7fff54b9a2a0, flags={i = 0}) at kernel/qeventloop.cpp:201
#36 0x00007f4ab04fea19 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x0000000000403d17 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.4/kontact/src/main.cpp:218
Warning: the current language does not match this frame.

This bug may be a duplicate of or related to bug 217249

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-31 01:14:52 UTC
The backtrace matches bug 163071, so it could be related. Regards
Comment 2 Christophe Marin 2010-03-26 23:29:40 UTC

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