Version: 1.9.1 (using KDE 3.5.2, compiled sources) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.16-davidb I found that all my expiry settings had been lost somewhere along the line. So I went to renew them. Checked numbers of days, permanent deletion, clicked expire. Crash. Crash dump has no useful information. Restarted kmail, repeated, crash. However, if I manually move one message, any message, out of the folder before expiring, it works just fine.
Can you try this test: 1. Select a message that is older than the expiry period, and change the expiry on the folder. 2. Select a message that is newer (e.g. today) than the expiry period, and change the expiry on the folder. Does the first one crash, and not the second?
The first one crashed, the second (newer selection) did not!
I think I can also reproduce this bug, I have kmail 1.9.3 and KDE 3.5.4. I found kmail crashing today when I activated expiring of mails older than 30 days (for read as well as unread mail). I noticed later the folder only contains mail until 10.2005, so the expiring should in fact delete all the mail in the folder, but instead it crashes kmail, 100% reproducible... Backtrace: [KCrash handler] #6 0xa7ddf76c in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so #7 0xa7dd1ef9 in KMCommand::slotPostTransfer () from /usr/lib/libkmailprivate.so #8 0xa7dd9ab6 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so #9 0xa7dd9d9b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so #10 0xa7dd9e33 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so #11 0xa735ab87 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #12 0xa7dd21fe in KMCommand::messagesTransfered () from /usr/lib/libkmailprivate.so #13 0xa7dda944 in KMCommand::transferSelectedMsgs () from /usr/lib/libkmailprivate.so #14 0xa7ddaaa7 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so #15 0xa7dd9ac8 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so #16 0xa7dd9d9b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so #17 0xa7dd9e33 in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so #18 0xa735ab87 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0xa76e3bcb in QSignal::signal () from /usr/lib/libqt-mt.so.3 #20 0xa737a70a in QSignal::activate () from /usr/lib/libqt-mt.so.3 #21 0xa73820dc in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #22 0xa72f2aea in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #23 0xa72f4907 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #24 0xa6fbf52e in KApplication::notify () from /usr/lib/libkdecore.so.4 #25 0xa72863d1 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #26 0xa72e54e7 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #27 0xa729a71f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #28 0xa730d03d in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #29 0xa730ce5e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #30 0xa72f4683 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #31 0x0804a094 in ?? () #32 0xaffbfff4 in ?? () #33 0xaffc01e0 in ?? () #34 0x00000000 in ?? ()
I tried this experiment and cannot manage a crash. Can anyone who reported this crash perhaps rebuild the kdepim 3.5.4 source with --enable-debug=full and try again to get a backtrace? This may provide us with actual line numbers in the source code where the crash is happening.
I tried this on two different folders with mail older than 30 day but without any crash.
I get this crash - KDE 3.5.4 (Fedora Core 5). I came to bugs.kde.org to file a new bug, but this seems to be the one. Tried 3 times, got a crash each time. I installed the debuginfo packages in order to produce a backtrace, but then it stopped crashing. Otherwise, it looked like the one above. If I get it again, I'll post here.
*** Bug 134080 has been marked as a duplicate of this bug. ***
*** Bug 131692 has been marked as a duplicate of this bug. ***
*** Bug 134089 has been marked as a duplicate of this bug. ***
*** Bug 130305 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 108971 ***