Bug 220600 - navigating w/ keyboard on imap, threaded view, crash
Summary: navigating w/ keyboard on imap, threaded view, crash
Status: RESOLVED DUPLICATE of bug 163071
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-29 23:07 UTC by bradgers
Modified: 2010-01-27 13:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bradgers 2009-12-29 23:07:46 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-686 i686

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb6acfa66 in memcpy () from /lib/i686/cmov/libc.so.6
#7  0xbf9c31d8 in ?? ()
#8  0xb0a7e07d in QList<KMMessage*>::detach_helper (this=0xbf9c31d8) at /usr/include/qt4/QtCore/qlist.h:524
#9  0xb0cf69a8 in QList (this=0x83b0468) at /usr/include/qt4/QtCore/qlist.h:111
#10 KMail::FolderJob::msgList (this=0x83b0468) at ../../kmail/folderjob.cpp:120
#11 0xb0b85a4b in KMAcctImap::ignoreJobsForMessage (this=0x85c37a0, msg=0x900a380) at ../../kmail/kmacctimap.cpp:215
#12 0xb0b9c9f5 in KMFolderImap::ignoreJobsForMessage (this=0x85ae990, msg=0x900a380) at ../../kmail/kmfolderimap.cpp:1564
#13 0xb0cb2816 in KMMoveCommand::execute (this=0x9016c10) at ../../kmail/kmcommands.cpp:2095
#14 0xb0c975e2 in KMCommand::slotPostTransfer (this=0x9016c10, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:274
#15 0xb0ca186c in KMCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf9c34fc) at ./kmcommands.moc:87
#16 0xb0cb455a in KMMoveCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c34fc) at ./kmcommands.moc:1706
#17 0xb0cb4622 in KMTrashMsgCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf9c34fc) at ./kmcommands.moc:1758
#18 0xb77ab303 in QMetaObject::activate (sender=0x9016c10, from_signal_index=4, to_signal_index=4, argv=0xbf9c34fc) at kernel/qobject.cpp:3112
#19 0xb77abf42 in QMetaObject::activate (sender=0x9016c10, m=0xb10c3634, local_signal_index=0, argv=0xbf9c34fc) at kernel/qobject.cpp:3186
#20 0xb0c934f3 in KMCommand::messagesTransfered (this=0x9016c10, _t1=KMCommand::OK) at ./kmcommands.moc:102
#21 0xb0cb0ab4 in KMCommand::transferSelectedMsgs (this=0x9016c10) at ../../kmail/kmcommands.cpp:368
#22 0xb0cb0d03 in KMCommand::slotStart (this=0x9016c10) at ../../kmail/kmcommands.cpp:266
#23 0xb0ca187b in KMCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf9c36f8) at ./kmcommands.moc:86
#24 0xb0cb455a in KMMoveCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c36f8) at ./kmcommands.moc:1706
#25 0xb0cb4622 in KMTrashMsgCommand::qt_metacall (this=0x9016c10, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf9c36f8) at ./kmcommands.moc:1758
#26 0xb77ab303 in QMetaObject::activate (sender=0x85db918, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#27 0xb77abf42 in QMetaObject::activate (sender=0x85db918, m=0xb7886d88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#28 0xb77b1007 in QSingleShotTimer::timeout (this=0x85db918) at .moc/release-shared/qtimer.moc:76
#29 0xb77b112c in QSingleShotTimer::timerEvent (this=0x85db918) at kernel/qtimer.cpp:298
#30 0xb77a639f in QObject::event (this=0x85db918, e=0xbf9c3b7c) at kernel/qobject.cpp:1074
#31 0xb6dd5a94 in QApplicationPrivate::notify_helper (this=0x823ddb0, receiver=0x85db918, e=0xbf9c3b7c) at kernel/qapplication.cpp:4065
#32 0xb6dddbee in QApplication::notify (this=0xbf9c3f2c, receiver=0x85db918, e=0xbf9c3b7c) at kernel/qapplication.cpp:3605
#33 0xb7c980fd in KApplication::notify (this=0xbf9c3f2c, receiver=0x85db918, event=0xbf9c3b7c) at ../../kdeui/kernel/kapplication.cpp:302
#34 0xb77961eb in QCoreApplication::notifyInternal (this=0xbf9c3f2c, receiver=0x85db918, event=0xbf9c3b7c) at kernel/qcoreapplication.cpp:610
#35 0xb77c4e21 in QCoreApplication::sendEvent (this=0x8230a84) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QTimerInfoList::activateTimers (this=0x8230a84) at kernel/qeventdispatcher_unix.cpp:580
#37 0xb77c1317 in timerSourceDispatch (source=0x8230ac0) at kernel/qeventdispatcher_glib.cpp:184
#38 idleTimerSourceDispatch (source=0x8230ac0) at kernel/qeventdispatcher_glib.cpp:231
#39 0xb5214f28 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#40 0xb52186b3 in ?? () from /lib/libglib-2.0.so.0
#41 0xb5218838 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#42 0xb77c1041 in QEventDispatcherGlib::processEvents (this=0x822f6e0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#43 0xb6e75305 in QGuiEventDispatcherGlib::processEvents (this=0x822f6e0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#44 0xb779483a in QEventLoop::processEvents (this=0xbf9c3da0, flags=...) at kernel/qeventloop.cpp:149
#45 0xb7794c82 in QEventLoop::exec (this=0xbf9c3da0, flags=...) at kernel/qeventloop.cpp:201
#46 0xb77970d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#47 0xb6dd5917 in QApplication::exec () at kernel/qapplication.cpp:3525
#48 0x0804bd40 in main (argc=1, argv=0xbf9c4124) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-30 03:04:59 UTC
- Were you deleting some message or marking it as spam?
This looks related to bug 163071. Regards
Comment 2 Dario Andres 2010-01-20 23:43:53 UTC
Waiting for feedback.
Comment 3 bradgers 2010-01-21 07:41:01 UTC
Deleting messages.  Generally if I delete a message, Kmail tries then
to shift it to my local trash folder.  If I then try to delete another
message while the first message is transferring, it'll crash pretty
reliably.  I don't use kontact spam capabilities.
Comment 4 Dario Andres 2010-01-27 13:57:03 UTC
Thanks

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