Application that crashed: kmail Version of the application: 1.12.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 KMFilterMgr::deref (this=0x0, force=false) at ../../kmail/kmfiltermgr.cpp:365 #7 0x00ddf034 in KMail::AccountManager::processNextCheck (this=0x9fc4590, _newMail=false) at ../../kmail/accountmanager.cpp:175 #8 0x00de05b8 in KMail::AccountManager::qt_metacall (this=0x9fc4590, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbff4c3b4) at ./accountmanager.moc:96 #9 0x00a61263 in QMetaObject::activate (sender=0x9fb1c80, from_signal_index=4, to_signal_index=4, argv=0xbff4c3b4) at kernel/qobject.cpp:3113 #10 0x00a61ec2 in QMetaObject::activate (sender=0x9fb1c80, m=0x13a2f84, local_signal_index=0, argv=0xbff4c3b4) at kernel/qobject.cpp:3187 #11 0x00d4a4ff in KMAccount::finishedCheck (this=0x9fb1c80, _t1=false, _t2=KMAccount::CheckOK) at ./kmaccount.moc:162 #12 0x00d4aece in KMAccount::checkDone (this=0x9fb1c80, newmail=false, status=KMAccount::CheckOK) at ../../kmail/kmaccount.cpp:507 #13 0x00e5c5b0 in KMAcctImap::killAllJobs (this=0x9fb1c80, disconnectSlave=true) at ../../kmail/kmacctimap.cpp:198 #14 0x00e5c70f in ~KMAcctImap (this=0x9fb1c80, __in_chrg=<value optimized out>) at ../../kmail/kmacctimap.cpp:86 #15 0x00dde10e in qDeleteAll<QList<KMAccount*>::const_iterator> (this=0x9fc4590, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:350 #16 qDeleteAll<AccountList> (this=0x9fc4590, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:358 #17 ~AccountManager (this=0x9fc4590, __in_chrg=<value optimized out>) at ../../kmail/accountmanager.cpp:39 #18 0x00eca541 in KMKernel::cleanup (this=0xbff4c62c) at ../../kmail/kmkernel.cpp:1758 #19 0x0804a70c in main (argc=1, argv=0xbff4c8a4) at ../../kmail/main.cpp:148 This bug may be a duplicate of or related to bug 220883 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 195894 ***