Version: 1.9.7 (using 3.5.8, Gentoo) Compiler: Target: i686-pc-linux-gnu OS: Linux (i686) release 2.6.23-gentoo-r6 In the lower right corner, I observe the completion status of various transactions (one or several stacked progress indicators). Whenever I attempt to cancel any of those transactions by clicking the cross to the right of the progress indicator, kmail follows (sometimes after a bit of delay) with a crash. My mail servers are reached in the IMAP mode. However, this happens even with sending transactions using a remote SMTP server (not an IMAP operation). Thanks, Jan
Please attach a backtrace, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) . . . (no debugging symbols found) [KCrash handler] #6 0x421c0d3f in KMail::ActionScheduler::fetchTimeOut () from /usr/kde/3.5/lib/libkmailprivate.so #7 0x421c49f3 in KMail::ActionScheduler::qt_invoke () from /usr/kde/3.5/lib/libkmailprivate.so #8 0x4155941e in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #9 0x41559f60 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #10 0x4186de11 in QTimer::timeout () from /usr/qt/3/lib/libqt-mt.so.3 #11 0x4157a49e in QTimer::event () from /usr/qt/3/lib/libqt-mt.so.3 #12 0x414fe2e5 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 #13 0x414fee42 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 #14 0x4ec6128f in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4 #15 0x414f405a in QEventLoop::activateTimers () from /usr/qt/3/lib/libqt-mt.so.3 #16 0x414b10d4 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 #17 0x41513c9d in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 #18 0x41513b42 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 #19 0x414fde0b in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 #20 0x0804a621 in ?? () #21 0xbfb78b70 in ?? () #22 0xbfb78d60 in ?? () #23 0x00000000 in ?? ()
*** This bug has been marked as a duplicate of 155026 ***