Bug 195598 - Kmail crashes when reorganizing (moving) emails between accounts
Summary: Kmail crashes when reorganizing (moving) emails between accounts
Status: RESOLVED DUPLICATE of bug 163071
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-07 21:44 UTC by Arthur Pemberton
Modified: 2009-06-07 22:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Kmail KCrash (4.53 KB, text/plain)
2009-06-07 21:46 UTC, Arthur Pemberton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Pemberton 2009-06-07 21:44:50 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Fedora RPMs

Kmail crashes very often for it, this time I had all the debug symbols in place and KCrash didn't suggest against filing a bug.

All I was doing, is moving email from the inbox of one IMAP account, to sub-folders of another account I use for archival. And then Kmail goes poof. It does this fairly frequently.
Comment 1 Arthur Pemberton 2009-06-07 21:46:20 UTC
Created attachment 34350 [details]
Kmail KCrash
Comment 2 Dario Andres 2009-06-07 22:26:07 UTC
Pasted backtrace from comment 1:
----

Application: KMail (kmail), signal SIGSEGV
[Current thread is 1 (Thread 0xb7fb5770 (LWP 4178))]

Thread 1 (Thread 0xb7fb5770 (LWP 4178)):
[KCrash Handler]
#6  QBasicAtomicInt::ref () at /usr/include/QtCore/qatomic_i386.h:120
#7  QList () at /usr/include/QtCore/qlist.h:111
#8  KMail::FolderJob::msgList (this=0xaf56f98) at /usr/src/debug/kdepim-4.2.3/kmail/folderjob.cpp:120
#9  0x02236cdb in KMAcctImap::ignoreJobsForMessage (this=0x9abf550, msg=0xaf1a068) at /usr/src/debug/kdepim-4.2.3/kmail/kmacctimap.cpp:215
#10 0x0224b435 in KMFolderImap::ignoreJobsForMessage (this=0x9cc36d0, msg=0xaf1a068) at /usr/src/debug/kdepim-4.2.3/kmail/kmfolderimap.cpp:1562
#11 0x02345194 in KMMoveCommand::execute (this=0xa80bec8) at /usr/src/debug/kdepim-4.2.3/kmail/kmcommands.cpp:2089
#12 0x02333392 in KMCommand::slotPostTransfer (this=0xa80bec8, result=KMCommand::OK) at /usr/src/debug/kdepim-4.2.3/kmail/kmcommands.cpp:276
#13 0x0233d714 in KMCommand::qt_metacall (this=0xa80bec8, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfbe4fcc) at /usr/src/debug/kdepim-4.2.3/i386-redhat-linux-gnu/kmail/kmcommands.moc:87
#14 0x0233dc0a in KMMoveCommand::qt_metacall (this=0xa80bec8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfbe4fcc) at /usr/src/debug/kdepim-4.2.3/i386-redhat-linux-gnu/kmail/kmcommands.moc:1706
#15 0x06448a08 in QMetaObject::activate (sender=0xa80bec8, from_signal_index=4, to_signal_index=4, argv=0xbfbe4fcc) at kernel/qobject.cpp:3069
#16 0x0644a192 in QMetaObject::activate (sender=0xa80bec8, m=0x27239d4, local_signal_index=0, argv=0xbfbe4fcc) at kernel/qobject.cpp:3143
#17 0x0232eef3 in KMCommand::messagesTransfered (this=0xa80bec8, _t1=KMCommand::OK) at /usr/src/debug/kdepim-4.2.3/i386-redhat-linux-gnu/kmail/kmcommands.moc:102
#18 0x02347b84 in KMCommand::transferSelectedMsgs (this=0xa80bec8) at /usr/src/debug/kdepim-4.2.3/kmail/kmcommands.cpp:370
#19 0x02347d73 in KMCommand::slotStart (this=0xa80bec8) at /usr/src/debug/kdepim-4.2.3/kmail/kmcommands.cpp:268
#20 0x0233d723 in KMCommand::qt_metacall (this=0xa80bec8, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfbe51a8) at /usr/src/debug/kdepim-4.2.3/i386-redhat-linux-gnu/kmail/kmcommands.moc:86
#21 0x0233dc0a in KMMoveCommand::qt_metacall (this=0xa80bec8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfbe51a8) at /usr/src/debug/kdepim-4.2.3/i386-redhat-linux-gnu/kmail/kmcommands.moc:1706
#22 0x06448a08 in QMetaObject::activate (sender=0xabd7d98, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#23 0x0644a192 in QMetaObject::activate (sender=0xabd7d98, m=0x6527c48, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#24 0x0644de07 in QSingleShotTimer::timeout (this=0xabd7d98) at .moc/release-shared/qtimer.moc:76
#25 0x0644df2c in QSingleShotTimer::timerEvent (this=0xabd7d98) at kernel/qtimer.cpp:298
#26 0x06442ebf in QObject::event (this=0xabd7d98, e=0xbfbe562c) at kernel/qobject.cpp:1082
#27 0x0369fcec in QApplicationPrivate::notify_helper (this=0x9a6f380, receiver=0xabd7d98, e=0xbfbe562c) at kernel/qapplication.cpp:4084
#28 0x036a7fce in QApplication::notify (this=0xbfbe5948, receiver=0xabd7d98, e=0xbfbe562c) at kernel/qapplication.cpp:3631
#29 0x069424fd in KApplication::notify (this=0xbfbe5948, receiver=0xabd7d98, event=0xbfbe562c) at /usr/src/debug/kdelibs-4.2.3/kdeui/kernel/kapplication.cpp:307
#30 0x0643275b in QCoreApplication::notifyInternal (this=0xbfbe5948, receiver=0xabd7d98, event=0xbfbe562c) at kernel/qcoreapplication.cpp:602
#31 0x06461a41 in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#32 QTimerInfoList::activateTimers (this=0x9a71d14) at kernel/qeventdispatcher_unix.cpp:572
#33 0x0645e230 in timerSourceDispatch (source=0x9a71ce0) at kernel/qeventdispatcher_glib.cpp:164
#34 0x00138258 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#35 0x0013b903 in ?? () from /lib/libglib-2.0.so.0
#36 0x0013bac1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#37 0x0645e188 in QEventDispatcherGlib::processEvents (this=0x9a4e2f8, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:323
#38 0x0373f665 in QGuiEventDispatcherGlib::processEvents (this=0x9a4e2f8, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#39 0x06430d8a in QEventLoop::processEvents (this=0xbfbe5850, flags={i = 36}) at kernel/qeventloop.cpp:149
#40 0x064311ca in QEventLoop::exec (this=0xbfbe5850, flags={i = 0}) at kernel/qeventloop.cpp:200
#41 0x06433679 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#42 0x0369fb67 in QApplication::exec () at kernel/qapplication.cpp:3553
#43 0x0804a360 in main (argc=) at /usr/src/debug/kdepim-4.2.3/kmail/main.cpp:146
Comment 3 Dario Andres 2009-06-07 22:29:13 UTC
Backtrace is like bug 163071. Do you remember if you deleted some message? Thanks
Comment 4 Arthur Pemberton 2009-06-07 22:41:11 UTC
Yes, I do believe that I did.
Comment 5 Dario Andres 2009-06-07 22:41:43 UTC
Ok, Thanks.
Marking as duplicate

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