[Bug 109722] KMail crashed after deleting mail from IMAP folder

Christian McHugh <[email protected]>
Newsgroups gmane.comp.kde.devel.kmail
Message-ID <[email protected]>
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=109722         




------- Additional Comments From mchugh19 yahoo com  2007-04-30 19:16 -------
I've also experienced a kmail crash while trying to delete mail. 

Here is the backtrace from kubuntu 7.04:
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1243445552 (LWP 8027)]
[New Thread -1286628464 (LWP 8031)]
[New Thread -1278235760 (LWP 8030)]
[New Thread -1269843056 (LWP 8029)]
[New Thread -1261450352 (LWP 8028)]
[KCrash handler]
#6  FolderStorage::moveMsg (this=0x83dc250, msglist= 0xbfdcccdc, 
    aIndex_ret=0xbfdccdd8)
    at /build/buildd/kdepim-3.5.6/./kmail/kmmsgbase.h:146
#7  0xb4f9dd53 in KMFolder::moveMsg (this=0x83dc148, q= 0xbfdccd90, 
    index_return=0xbfdccdd8)
    at /build/buildd/kdepim-3.5.6/./kmail/kmfolder.cpp:424
#8  0xb501e811 in KMMoveCommand::execute (this=0x889d728)
    at /build/buildd/kdepim-3.5.6/./kmail/kmcommands.cpp:2152
#9  0xb4f8b329 in KMCommand::slotPostTransfer (this=0x889d728, 
    result=KMCommand::OK)
    at /build/buildd/kdepim-3.5.6/./kmail/kmcommands.cpp:257
#10 0xb501fe46 in KMCommand::qt_invoke (this=0x889d728, _id=5, _o=0xbfdccf34)
    at ./kmcommands.moc:148
#11 0xb502021b in KMMenuCommand::qt_invoke (this=0x889d728, _id=5, 
    _o=0xbfdccf34) at ./kmcommands.moc:2801
#12 0xb50202a7 in KMMoveCommand::qt_invoke (this=0x889d728, _id=5, 
    _o=0xbfdccf34) at ./kmcommands.moc:2984
#13 0xb502031b in KMDeleteMsgCommand::qt_invoke (this=0x889d728, _id=5, 
    _o=0xbfdccf34) at ./kmcommands.moc:3059
#14 0xb6f2388b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb4f8b44e in KMCommand::messagesTransfered (this=0x889d728, 
    t0=KMCommand::OK) at ./kmcommands.moc:126
#16 0xb5080471 in KMCommand::transferSelectedMsgs (this=0x889d728)
    at /build/buildd/kdepim-3.5.6/./kmail/kmcommands.cpp:352
#17 0xb50805d7 in KMCommand::slotStart (this=0x889d728)
    at /build/buildd/kdepim-3.5.6/./kmail/kmcommands.cpp:249
#18 0xb501fe58 in KMCommand::qt_invoke (this=0x889d728, _id=4, _o=0xbfdcd0d8)
    at ./kmcommands.moc:147
#19 0xb502021b in KMMenuCommand::qt_invoke (this=0x889d728, _id=4, 
    _o=0xbfdcd0d8) at ./kmcommands.moc:2801
#20 0xb50202a7 in KMMoveCommand::qt_invoke (this=0x889d728, _id=4, 
    _o=0xbfdcd0d8) at ./kmcommands.moc:2984
#21 0xb502031b in KMDeleteMsgCommand::qt_invoke (this=0x889d728, _id=4, 
    _o=0xbfdcd0d8) at ./kmcommands.moc:3059
#22 0xb6f2388b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb72afae0 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6f4381e in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6f4b234 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6ebaa60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6ebc88f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb75f6ce2 in KApplication::notify (this=0xbfdcd73c, receiver=0x8190f90, 
    event=0xbfdcd428)
    at /build/buildd/kdelibs-3.5.6/./kdecore/kapplication.cpp:550
#29 0xb6e4d1e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6ead4ab in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6e61d25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6ed5136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6ed4f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6ebc609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x08061e25 in main (argc=1, argv=0x11)
    at /build/buildd/kdepim-3.5.6/./kontact/src/main.cpp:163
#36 0xb7690ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x08059151 in _start ()
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.