| Summary: | Crashed after moving a corrupted mail to IMAP account | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Florian Faber <kdebug> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | mailinglist, w.richert |
| Priority: | NOR | ||
| Version: | 1.9.5 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Possible dupe of this: http://bugs.kde.org/show_bug.cgi?id=128593 (and) http://bugs.kde.org/show_bug.cgi?id=134702 I'm seeing this as well. Also on a Gentoo system with KMail 1.9.5, GCC 4.1.1. The stack trace is the same. I can reliable reproduce this when I do an "Expire All Folders" and I have some filters set up on a few IMAP folders to move old messages around. The referenced bugs (above) seem to point to a corrupted message. I have access to the IMAP server and I'd love any kind of suggestion as to how to track down the corrupted message. *** Bug 140684 has been marked as a duplicate of this bug. *** *** Bug 140740 has been marked as a duplicate of this bug. *** I have the same backtrace too. KMail 1.9.5 crashed when moving some mails from an IMAP folder to a local one. crash confirmed using pim+ branch r634247. I've plain imap connection, selected ~10 email's and pressed trash icon.
#16 0xb7c2d130 in FolderStorage::moveMsg (this=0x8394c30, msglist=@0xbfcad7ec,
aIndex_ret=0xbfcad8d4) at folderstorage.cpp:604
#17 0xb7c118e0 in KMFolder::moveMsg (this=0x83cc8c0, q=@0xbfcad88c,
index_return=0xbfcad8d4) at kmfolder.cpp:425
#18 0xb7d4a8a0 in KMMoveCommand::execute (this=0x80b2e68)
at kmcommands.cpp:2165
#19 0xb7d550bd in KMCommand::slotPostTransfer (this=0x80b2e68,
result=KMCommand::OK) at kmcommands.cpp:257
#20 0xb7d553f6 in KMCommand::qt_invoke (this=0x80b2e68, _id=5, _o=0xbfcada44)
at kmcommands.moc:148
#21 0xb7d5592b in KMMenuCommand::qt_invoke (this=0x80b2e68, _id=5,
i get this crash several times a week when deleting mails. gentoo, CFLAGS="-march=pentium3 -O2 -pipe", currently kmail 1.9.6-r1 but this has been going on for at least a year now. *** Bug 143372 has been marked as a duplicate of this bug. *** |
Version: 1.9.5 (using KDE KDE 3.5.5) Installed from: Compiled From Sources Compiler: gcc (GCC) 4.1.1 (Gentoo 4.1.1-r3) CFLAGS="-O2 -march=k8 -pipe -ggdb" OS: Linux Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47157281142480 (LWP 30853)] [New Thread 1107310912 (LWP 30857)] [New Thread 1098918208 (LWP 30856)] [New Thread 1090525504 (LWP 30855)] [New Thread 1082132800 (LWP 30854)] [KCrash handler] #5 FolderStorage::moveMsg (this=0x6a7200, msglist=@0x7fff08afaa40, aIndex_ret=<value optimized out>) at kmmsgbase.h:146 #6 0x00002ae3a2335d65 in KMFolder::moveMsg (this=0x6a6e00, q=<value optimized out>, index_return=0x7fff08afac18) at kmfolder.cpp:424 #7 0x00002ae3a2399a9b in KMMoveCommand::execute (this=0x6ce660) at kmcommands.cpp:1987 #8 0x00002ae3a231f800 in KMCommand::slotPostTransfer (this=0x6ce660, result=KMCommand::OK) at kmcommands.cpp:256 #9 0x00002ae3a239b063 in KMCommand::qt_invoke (this=0x6ce660, _id=5, _o=0x7fff08afad40) at kmcommands.moc:148 #10 0x00002ae3a239b2e9 in KMMenuCommand::qt_invoke (this=0x7fff08afaa40, _id=145730112, _o=0x7fff08afac18) at kmcommands.moc:2509 #11 0x00002ae3a239b36d in KMMoveCommand::qt_invoke (this=0x6ce660, _id=5, _o=0x7fff08afad40) at kmcommands.moc:2692 #12 0x00002ae3a69d2a0c in QObject::activate_signal (this=0x6ce660, clist=<value optimized out>, o=0x7fff08afad40) at kernel/qobject.cpp:2356 #13 0x00002ae3a231f92c in KMCommand::messagesTransfered ( this=<value optimized out>, t0=KMCommand::OK) at kmcommands.moc:126 #14 0x00002ae3a23ee09d in KMCommand::transferSelectedMsgs (this=0x6ce660) at kmcommands.cpp:351 #15 0x00002ae3a239b077 in KMCommand::qt_invoke (this=0x6ce660, _id=4, _o=0x7fff08afaec0) at kmcommands.moc:147 #16 0x00002ae3a239b2e9 in KMMenuCommand::qt_invoke (this=0x7fff08afaa40, _id=145730112, _o=0x7fff08afac18) at kmcommands.moc:2509 #17 0x00002ae3a239b36d in KMMoveCommand::qt_invoke (this=0x6ce660, _id=4, _o=0x7fff08afaec0) at kmcommands.moc:2692 #18 0x00002ae3a69d2a0c in QObject::activate_signal (this=0x87cf00, clist=<value optimized out>, o=0x7fff08afaec0) at kernel/qobject.cpp:2356 #19 0x00002ae3a6caffe5 in QSignal::signal (this=<value optimized out>, t0=@0x87cf50) at .moc/release-shared-mt/moc_qsignal.cpp:100 #20 0x00002ae3a69eb435 in QSignal::activate (this=0x87cf00) at kernel/qsignal.cpp:212 #21 0x00002ae3a69f19c8 in QSingleShotTimer::event (this=0x87ceb0) at kernel/qtimer.cpp:286 #22 0x00002ae3a697c885 in QApplication::internalNotify ( this=<value optimized out>, receiver=0x87ceb0, e=0x7fff08afb1c0) at kernel/qapplication.cpp:2635 #23 0x00002ae3a697d487 in QApplication::notify (this=0x7fff08afb420, receiver=0x87ceb0, e=0x7fff08afb1c0) at kernel/qapplication.cpp:2358 #24 0x00002ae3a5dd53df in KApplication::notify (this=0x7fff08afb420, receiver=0x87ceb0, event=0x7fff08afb1c0) at kapplication.cpp:550 #25 0x00002ae3a6972fc2 in QEventLoop::activateTimers ( this=<value optimized out>) at kernel/qapplication.h:496 #26 0x00002ae3a6933f22 in QEventLoop::processEvents (this=0x55f9b0, flags=0) at kernel/qeventloop_x11.cpp:389 #27 0x00002ae3a6991062 in QEventLoop::enterLoop (this=0x7fff08afaa40) at kernel/qeventloop.cpp:198 #28 0x00002ae3a6990f12 in QEventLoop::exec (this=0x7fff08afaa40) at kernel/qeventloop.cpp:145 #29 0x0000000000402d0d in main (argc=<value optimized out>, argv=<value optimized out>) at main.cpp:110 #30 0x00002ae3a8db6374 in __libc_start_main (main=0x402bd0 <main>, argc=1, ubp_av=0x7fff08afb8f8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff08afb8e8) at libc-start.c:238 #31 0x0000000000402a99 in _start () Current language: auto; currently c