Application: kmail (1.13.5) KDE Platform Version: 4.6.1 (4.6.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-27-generic i686 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: I've got some problems with connection to my mailbox.(IMAP) Kmail was in fetching progress. I didn't want to wait and closed Kmail then it crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb789d780 (LWP 7723))] Thread 2 (Thread 0xb24b8b70 (LWP 7727)): #0 0x04f6e9a0 in g_main_context_check () from /lib/libglib-2.0.so.0 #1 0x04f6f45e in ?? () from /lib/libglib-2.0.so.0 #2 0x04f6f848 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x089cb59f in QEventDispatcherGlib::processEvents (this=0xa397df0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #4 0x0899b609 in QEventLoop::processEvents (this=0xb24b8220, flags=) at kernel/qeventloop.cpp:149 #5 0x0899ba8a in QEventLoop::exec (this=0xb24b8220, flags=...) at kernel/qeventloop.cpp:201 #6 0x08897b7e in QThread::exec (this=0xa39c6f0) at thread/qthread.cpp:490 #7 0x0897a35b in QInotifyFileSystemWatcherEngine::run (this=0xa39c6f0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x0889adf9 in QThreadPrivate::start (arg=0xa39c6f0) at thread/qthread_unix.cpp:266 #9 0x013fecc9 in start_thread () from /lib/libpthread.so.0 #10 0x092ac69e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb789d780 (LWP 7723)): [KCrash Handler] #7 KMFilterMgr::ref (this=0x0) at ../../kmail/kmfiltermgr.cpp:360 #8 0x00dbff6b in KMail::AccountManager::processNextCheck (this=0x9e1dfe8, _newMail=false) at ../../kmail/accountmanager.cpp:230 #9 0x00dc0750 in KMail::AccountManager::singleCheckMail (this=0x9e1dfe8, account=0x0, interactive=true) at ../../kmail/accountmanager.cpp:157 #10 0x00e2f3d5 in KMail::ImapAccountBase::slotCheckQueuedFolders (this=0x9e47cb0) at ../../kmail/imapaccountbase.cpp:1158 #11 0x00e3f6b7 in KMail::ImapAccountBase::qt_metacall (this=0x9e47cb0, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf87b934) at ./imapaccountbase.moc:134 #12 0x00e46a5a in KMAcctImap::qt_metacall (this=0x9e47cb0, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf87b934) at ./kmacctimap.moc:83 #13 0x089a28ca in QMetaObject::metacall (object=0x9e47cb0, cl=20418548, idx=20, argv=0xbf87b934) at kernel/qmetaobject.cpp:237 #14 0x089b56ad in QMetaObject::activate (sender=0x9e47cb0, m=0x13697e4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3280 #15 0x00d2cf0f in KMAccount::finishedCheck (this=0x9e47cb0, _t1=false, _t2=KMAccount::CheckOK) at ./kmaccount.moc:174 #16 0x00d2d821 in KMAccount::checkDone (this=0x9e47cb0, newmail=false, status=KMAccount::CheckOK) at ../../kmail/kmaccount.cpp:515 #17 0x00e46fea in KMAcctImap::killAllJobs (this=0x9e47cb0, disconnectSlave=false) at ../../kmail/kmacctimap.cpp:204 #18 0x00e5ee89 in KMFolderImap::~KMFolderImap (this=0x9e0bc38, __in_chrg=<value optimized out>) at ../../kmail/kmfolderimap.cpp:95 #19 0x00d79332 in KMFolder::~KMFolder (this=0x9e2b9a8, __in_chrg=<value optimized out>) at ../../kmail/kmfolder.cpp:170 #20 0x00dcd5d6 in qDeleteAll<QList<KMFolderNode*>::iterator> (begin=) at /usr/include/qt4/QtCore/qalgorithms.h:322 #21 0x00dca486 in KMFolderDir::~KMFolderDir (this=0x9e221d8, __in_chrg=<value optimized out>) at ../../kmail/kmfolderdir.cpp:91 #22 0x00dcd5d6 in qDeleteAll<QList<KMFolderNode*>::iterator> (begin=) at /usr/include/qt4/QtCore/qalgorithms.h:322 #23 0x00dcb3e0 in KMFolderRootDir::~KMFolderRootDir (this=0x9d96b14, __in_chrg=<value optimized out>) at ../../kmail/kmfolderdir.cpp:37 #24 0x00dcf4e6 in KMFolderMgr::~KMFolderMgr (this=0x9d96b08, __in_chrg=<value optimized out>) at ../../kmail/kmfoldermgr.cpp:54 #25 0x00eadba7 in KMKernel::cleanup (this=0xbf87bcb8) at ../../kmail/kmkernel.cpp:1800 #26 0x0804a898 in main (argc=3, argv=0xbf87bf44) at ../../kmail/main.cpp:158 Reported using DrKonqi
*** Bug 269968 has been marked as a duplicate of this bug. ***
Cannot reproduce with KMail2. The fix will be in kdepim 4.6
*** Bug 272546 has been marked as a duplicate of this bug. ***
*** Bug 277840 has been marked as a duplicate of this bug. ***