Version: 1.9.3 (using KDE KDE 3.5.3) Installed from: Mandriva RPMs Compiler: gcc-4.1.1 (GCC) 4.1.1 20060518 (prerelease) Target: i586-mandriva-linux-gnu; Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --enable-languages=c,c++,ada,fortran,objc,obj-c++,java --host=i586-mandriva-linux-gnu --with-system-zlib --enable-long-long --enable-__cxa_atexit --enable-clocale=gnu --disable-libunwind-exceptions --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --enable-gtk-cairo --enable-ssp --disable-libssp; Thread model: posix OS: Linux I have two cases where kmail crashed where it shouldn't... I was deleting somes files (all the files in my Junk mail directory in fact...), and all files where moved to trash directory Then I noticed that some of them where not marked as spam by spamassassin, I selected them all and marked as spam with the filter (present in my shortcut bar as a button). The filter mark them as spam and then move them in the junk directory. Then I choose to delete them all and while deleting the files, kmail crashed... The other crash is a little bit older and was while deleting some files from junk mail (I don't remember well, but I should have marked as spam in the junk mail dir that time instead of trash dir), then kmail crashed while moving them to trash (or final delete)
Created attachment 16898 [details] crash_kmail_marks_junk_mail_as_spam_remove_to_trash_after_automove_in_junk_dir_and_crash_when_delete_trash_spam_mails
Created attachment 16899 [details] crash_kmail_move_unrequested_file_trash
Created attachment 17483 [details] Backtrace when Kmail crashed while moving all message in a particular folder to trash
Created attachment 17847 [details] Kmail crashed when a message was being deleted.
Pasting first backtrace: #6 0xb5fa7074 in typeinfo for QChildEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0xb7c33615 in KMMoveCommand::execute (this=0x8532da8) at kmcommands.cpp:1899 #8 0xb7be85b4 in KMCommand::slotPostTransfer (this=0x8532da8, result=KMCommand::OK) at kmcommands.cpp:255 #9 0xb7c3ba9f in KMCommand::qt_invoke (this=0x8532da8, _id=5, _o=0xbf8728b4) at kmcommands.moc:148 #10 0xb7c3beeb in KMMenuCommand::qt_invoke (this=0x8532da8, _id=5, _o=0xbf8728b4) at kmcommands.moc:2436 #11 0xb7c3bfb3 in KMMoveCommand::qt_invoke (this=0x8532da8, _id=5, _o=0xbf8728b4) at kmcommands.moc:2619 #12 0xb5bc7c84 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb7bc7647 in KMCommand::messagesTransfered (this=0x8532da8, t0=KMCommand::OK) at kmcommands.moc:126 #14 0xb7c3cae8 in KMCommand::transferSelectedMsgs (this=0x8532da8) at kmcommands.cpp:350 #15 0xb7c3ccbc in KMCommand::slotStart (this=0x8532da8) at kmcommands.cpp:247 #16 0xb7c3bab4 in KMCommand::qt_invoke (this=0x8532da8, _id=4, _o=0xbf872a54) at kmcommands.moc:147 #17 0xb7c3beeb in KMMenuCommand::qt_invoke (this=0x8532da8, _id=4, _o=0xbf872a54) at kmcommands.moc:2436 #18 0xb7c3bfb3 in KMMoveCommand::qt_invoke (this=0x8532da8, _id=4, _o=0xbf872a54) at kmcommands.moc:2619 #19 0xb5bc7c84 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb5eabc86 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
The first backtrace is the same as the one in bug 127417, so I'll close this one as a dupe. I'll take a look at the other backtraces and see if I can recommend something *** This bug has been marked as a duplicate of 127417 ***
Backtrace in comment 4 is quite different. Tom, could you open a new report for that, with steps to reproduce the problem?