Version: (using KDE KDE 3.5.6) Installed from: Unlisted Binary Package Compiler: gcc version 4.1.1 20070105 OS: Linux After upgrade when I click 'Check mail in' for retrieve messages from local mailbox (/var/spool/mail/myuser), I get QGArray::at: Absolute index 0 out of range and crash: [KCrash handler]: #5 0xb7df889d in KMFolderMbox::createIndexFromContents () from /usr/lib/libkmailprivate.so #6 0xb7d841b5 in KMFolderMbox::open () from /usr/lib/libkmailprivate.so #7 0xb7c7c74b in KMFolder::open () from /usr/lib/libkmailprivate.so #8 0xb7db4004 in KMAcctLocal::preProcess () from /usr/lib/libkmailprivate.so #9 0xb7db43a0 in KMAcctLocal::processNewMail () from /usr/lib/libkmailprivate.so #10 0xb7d861eb in KMail::AccountManager::processNextCheck () from /usr/lib/libkmailprivate.so #11 0xb7d8629b in KMail::AccountManager::singleCheckMail () from /usr/lib/libkmailprivate.so #12 0xb7d86471 in KMail::AccountManager::intCheckMail () from /usr/lib/libkmailprivate.so #13 0xb7e279bb in KMMainWidget::slotCheckOneAccount () from /usr/lib/libkmailprivate.so #14 0xb7e57f88 in KMMainWidget::qt_invoke () from /usr/lib/libkmailprivate.so #15 0xb75be0af in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #16 0xb75be580 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0xb780a74a in QPopupMenu::activated () from /usr/lib/libqt-mt.so.3 #18 0xb7678c75 in QPopupMenu::actSig () from /usr/lib/libqt-mt.so.3 #19 0xb7679006 in QPopupMenu::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #20 0xb6607c7f in KPopupMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.4 #21 0xb75e4164 in QWidget::event () from /usr/lib/libqt-mt.so.3 #22 0xb757cc8c in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #23 0xb757d033 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #24 0xb7a62bca in KApplication::notify () from /usr/lib/libkdecore.so.4 #25 0xb752f298 in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3
A fix for this bug was just committed into the 3.5 branch yesterday.
*** Bug 141955 has been marked as a duplicate of this bug. ***