Summary: | Kontact crashes on startup after it crashed on filtering IMAP messages (backtraces inside) | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Daniel Hahler <kde-bugzilla> |
Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bflat1, em-kdebugs-2, franklin, itlistuser, kern, marcus |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | kontact-backtrace.txt |
Description
Daniel Hahler
2005-10-24 20:52:02 UTC
This looks similar to a crash I have been experiencing when using KDE 3.5 beta2 with Kontact 1.2 and KMail 1.8.92. Not sure what is triggering the crash, but when Kmail/Kontact crashes it appears to corrupt the on disk imap cache. KMail/Kontact will then crash every time I start them until I delete the cache. Anything that invalidates the cache allows kmail to start up again successfully. If it is useful I have rebuilt with debug and symbols so I could provide output and a backtrace. The same problem happens on both my laptop (GCC 4.0.2-r1) and my desktop (GCC 3.4.4-r1) although I have not observed any similar behaviour in KDE 3.4. I also tried clearing my .kde dir and starting from nothing but the problems persists. If it helps it has happened again on my desktop amd64 system. It is a Gentoo amd64 system, and I rebuilt KDE with symbols and debug enabled. This happens consistently and the fix is to delete a few files from .kde/share/apps/kmail/imap/ but it is really irritating as I then have to download the mails and set up the folders again. Also a lot of folders default to being sorted by sender or subject which never happened in 3.4. If I only delete a couple of files then some folders do retain their settings, but deleting them all always works. marcus@cryos ~ $ kmail kmail: KMKernel::KMKernel kdecore (KConfigSkeleton): Creating KConfigSkeleton (0x88dea0) kdecore (KConfigSkeleton): KConfigSkeleton::readConfig() libkdenetwork: creating new pgp object libkdenetwork: Kpgp: gpg found kmail: No Qt-native utf-7 codec found; registering QUtf7Codec from libkdenetwork kmail: [void KMKernel::init()] foldersPath (from config): '/home/marcus/Mail' kmail: instantating KPIM::IdentityManager kmail: Identity::readConfig(): UOID = 1269029220 for identity named "Default" kmail: Identity::readConfig(): UOID = 1615353041 for identity named "Gentoo" kmail: Identity::readConfig(): UOID = 2113785385 for identity named "Uni" kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: WARNING: [void KMFolderImap::setImapPath(const QString&)] ignoring empty path kmail: pPopFilter set kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-marcus/ksycoca kimproxy (kdelibs): App kopete, dcopObjectId KIMIface found, using it for presence info. kmail: KMailApplication::newInstance() kmail: KMKernel::openReader called QSplitter::panner 1 I QSplitter::panner 2 I QSplitter::panner 2 I QSplitter::panner 2 I kmail: [QTextCodec* KCharsets::codecForName(const QString&, bool&) const] kmail: Trying to find IBM852 in /usr/share/i18n/charmaps kmail: Loading gzipped charset... kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa29c20 ): KAccel object already contains an action name "delete" kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa29c20 ): KAccel object already contains an action name "edit" kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa29c20 ): KAccel object already contains an action name "display_message" kmail: slotListNamespaces - waiting for connection kmail: slotListNamespaces - waiting for connection kmail: slotListNamespaces - waiting for connection marcus@cryos ~ $ kmail: processNextCheck, remaining 1 kmail: for host imap.cryos.net current connections=0 and limit is 0 kmail: connection limit reached: false kmail: processing next mail check for Marcus kmail: check mail started - connections for host imap.cryos.net now is 1 kmail: processNewMail false,status=2 kmail: KMFolderImap::processNewMail - waiting for connection: ADSLGuide kmail: KMFolderImap::processNewMail - waiting for connection: Business kmail: KMFolderImap::processNewMail - waiting for connection: Amazon kmail: KMFolderImap::processNewMail - waiting for connection: Bytemark kmail: KMFolderImap::processNewMail - waiting for connection: Dabs kmail: KMFolderImap::processNewMail - waiting for connection: Easily kmail: KMFolderImap::processNewMail - waiting for connection: eBay kmail: KMFolderImap::processNewMail - waiting for connection: eCommodate kmail: KMFolderImap::processNewMail - waiting for connection: OpenHosting kmail: KMFolderImap::processNewMail - waiting for connection: Thawte kmail: KMFolderImap::processNewMail - waiting for connection: WCS kmail: KMFolderImap::processNewMail - waiting for connection: Zen kmail: KMFolderImap::processNewMail - waiting for connection: Dan kmail: KMFolderImap::processNewMail - waiting for connection: Drafts kmail: KMFolderImap::processNewMail - waiting for connection: Friends kmail: KMFolderImap::processNewMail - waiting for connection: Sent kmail: KMFolderImap::processNewMail - imapPath of Spam is empty! kmail: slotListNamespaces - waiting for connection kmail: slotListNamespaces - waiting for connection kmail: slotListNamespaces - waiting for connection *** KMail got signal 11 (Crashing) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = <unknown> pid = 30244 Backtrace if it is of use, Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912618150208 (LWP 30244)] 0x00002aaab142de84 in waitpid () from /lib/tls/libpthread.so.0 #0 0x00002aaab142de84 in waitpid () from /lib/tls/libpthread.so.0 #1 0x00002aaaaec6d33e in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:251 #2 0x00002aaab1d0d890 in killpg () from /lib/tls/libc.so.6 #3 0x0000000000000000 in ?? () #4 0x0000000000000000 in ?? () #5 0x0000000000000000 in ?? () #6 0x0000000200000002 in ?? () #7 0x0000000000000000 in ?? () #8 0x0000000000000000 in ?? () #9 0x0000000000000000 in ?? () #10 0x0000000000bcb2a0 in ?? () #11 0x00002aaaafd3456c in QUType_Null::convertTo () at qucom.cpp:49 I am afraid there is still quite a bit missing, may be I missed something when I rebuild or need to rebuild glibc/gcc with symbols. Created attachment 13225 [details]
kontact-backtrace.txt
This is a backtrace from a crash which resulted in kmail crashing every time I
started it again before deleting the cache files. If there is any more
information you need then please let me know, this issue is making kmail near
unusable.
This is currently crashing Kontact on startup here. I first get the error from Akregator that the storage engine is faulty (known and solved issue) and then Kontact crashes. From a rough look at the backtrace it seems to be KMail responsible for this. Probably identical to some other backtrace above, but I hope it can help to solve this. (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1241384736 (LWP 13609)] [KCrash handler] #7 0xb53ac989 in KMFolder::noContent () from /usr/lib/libkmailprivate.so #8 0xb55770f9 in KMAcctImap::processNewMail () from /usr/lib/libkmailprivate.so #9 0xb54dd74e in KMail::AccountManager::processNextCheck () from /usr/lib/libkmailprivate.so #10 0xb54dd90b in KMail::AccountManager::singleCheckMail () from /usr/lib/libkmailprivate.so #11 0xb54dde97 in KMail::AccountManager::checkMail () from /usr/lib/libkmailprivate.so #12 0xb5640176 in KMMainWidget::slotCheckMail () from /usr/lib/libkmailprivate.so #13 0xb56515a8 in KMMainWidget::qt_invoke () from /usr/lib/libkmailprivate.so #14 0xb6814929 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #15 0xb6b73e92 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #16 0xb6832344 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #17 0xb6839e88 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #18 0xb67abf80 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #19 0xb67ac172 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #20 0xb6ef6eec in KApplication::notify (this=0xbfe1c500, receiver=0x87b9590, event=0xbfe1b498) at kapplication.cpp:550 #21 0xb673cdb7 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #22 0xb679d99b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #23 0xb6750a84 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #24 0xb67c3cfb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #25 0xb67aac3f in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #26 0xb69c5320 in QDialog::exec () from /usr/lib/libqt-mt.so.3 #27 0xb71f10b7 in KMessageBox::createKMessageBox (dialog=0x8881ef0, icon=@0xbfe1b860, text=@0xbfe1b9d8, strlist=@0xbfe1b928, ask=@0x806aaf8, checkboxReturn=0x0, options=) at kmessagebox.cpp:309 #28 0xb71f17cb in KMessageBox::createKMessageBox (dialog=0x8881ef0, icon=QMessageBox::Critical, text=@0xbfe1b9d8, strlist=@0xbfe1b928, ask=@0x806aaf8, checkboxReturn=0x0, options=1, details=@0x806aaf8) at kmessagebox.cpp:146 #29 0xb71f1c52 in KMessageBox::errorListWId (parent_id=0, text=@0xbfe1b9d8, strlist=@0xbfe1b928, caption=@0xbfe1b9d4, options=) at kmessagebox.cpp:772 #30 0xb721d8df in KMessageBox::error (parent=0x0, text=@0xbfe1b9d8, caption=@0xbfe1b9d4, options=1) at kmessagebox.cpp:737 #31 0xb50e9634 in Akregator::Part::Part () from /usr/lib/kde3/libakregatorpart.so #32 0xb510176d in KParts::GenericFactory<Akregator::Part>::createPartObject () from /usr/lib/kde3/libakregatorpart.so #33 0xb762ec26 in KParts::Factory::createPart (this=0x886a718, parentWidget=0x816d2f0, widgetName=0x0, parent=0x816d2f0, name=0xb7d98875 "kontact", classname=0xb764b7fd "KParts::ReadOnlyPart", args=@0xbfe1bafc) at factory.cpp:44 #34 0xb7d96ff8 in Kontact::Core::createPart () from /usr/lib/libkpinterfaces.so.1 #35 0xb7d973d2 in Kontact::Plugin::loadPart () from /usr/lib/libkpinterfaces.so.1 #36 0xb5a36dee in Akregator::Plugin::createPart () from /usr/lib/kde3/libkontact_akregator.so #37 0xb7d940cc in Kontact::Plugin::part () from /usr/lib/libkpinterfaces.so.1 #38 0x0805cc18 in ?? () #39 0x0827b3b0 in ?? () #40 0x00000000 in ?? () #41 0xb6d2b7b8 in ?? () #42 0xb6286cd0 in ?? () from /usr/lib/libstdc++.so.6 #43 0xb712dd90 in KGradientSelector::drawContents () at qimage.h:401 #44 0x0805c308 in ?? () #45 0x0816d2f0 in ?? () #46 0x0827b3b0 in ?? () #47 0x08869a50 in ?? () #48 0x0826fed0 in ?? () #49 0x0885def0 in ?? () #50 0x08218aa8 in ?? () #51 0x081a6dc8 in ?? () #52 0xb6260c71 in operator delete () from /usr/lib/libstdc++.so.6 #53 0x08059ee6 in ?? () #54 0x0816d2f0 in ?? () #55 0x0819f34c in ?? () #56 0xbfe1bcf8 in ?? () #57 0x08059edc in ?? () #58 0xb6ca7630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #59 0x08078590 in ?? () #60 0x083e7840 in ?? () #61 0xbfe1c548 in ?? () #62 0x081a3f3c in ?? () #63 0x0816d2f0 in ?? () #64 0x083e7790 in ?? () #65 0xbfe1c548 in ?? () #66 0x081a3f3c in ?? () #67 0x0816d2f0 in ?? () #68 0xbfe1bd58 in ?? () #69 0x0805f5be in ?? () #70 0x0816d2f0 in ?? () #71 0xbfe1bd34 in ?? () #72 0x081a3f3c in ?? () #73 0x0805f32e in ?? () #74 0x081a7068 in ?? () #75 0x00000000 in ?? () #76 0xb749e410 in KFileMetaInfo::KFileMetaInfo () at kfilemetainfo.cpp:304 Just to add that this still happens with 3.5.0_rc1 too. Even after deleting all imap cache files. If kmail crashes for any reason on the next start it crashes every time until the imap cache files are removed. I had the same thing happen to me with KDE 3.5, KMail 1.9, Qt 3.3.4 on Gentoo, running inside Kontact. KMail crashed while filtering messages incoming in my IMAP mailbox, on restarting, KMail crashed before it had started completely. After restarting it again it began redownloading all messages in by IMAP mailbox and filtering them, sometimes crashing in the process. I haven't had the problem when using CTRL-J to filter marked messages, but I only do that with 15-20 messages at a time, perhaps that has something to do with it? In my case I know it isn't filtering as I don't do any in kmail (use procmail server side). It is a corrupted cache and no matter how many times I restart it I get a crash until I delete the files in .kde/share/apps/kmail/imap (I only delete the visible files now - not all the .files). The second and third backtraces, as well as that from comment #4 are dealt with in bug 113329. I seem to be having the same problem. Basically, if kontact is abnormally shutdown, or if I accidentally try to start a second copy, 9 out of 10 ten times, Kontact will crash, then continue to seg fault on restarting. The fault is in the IMAP handling (traceback similar to those shown by other users). Most times if I clear everything in .kde/share/apps/kmail/imap I can get it running again. 1 out of 10 of these crashes, kmail is unable to restart because of a mime file type error (sorry I don't have the message). The only cure I have found is re-installing KDE. To the best of my knowledge I had no filtering turned on when the crash occurs. I consider this a very high priority bug because it occurs when accidentally launching a second copy of kontact and also happens if I shutdown kontact while my system is running, then restart kontact (apparently some part of kmail remains active thus destroying the cache the next time the program is started). *** Bug 128560 has been marked as a duplicate of this bug. *** *** Bug 129231 has been marked as a duplicate of this bug. *** Hello, I reported bug 130010 which has been dupped to 128560 (which in turn dups to here). Sorry for the dup but really 128560 did not show up on the "Check if dup" list when I entered my bug. Now effectively bug 130010, 128560 and 129231 have been marked duplicates of this bug, but this bug involves IMAP, right? I do not have any IMAP accounts at all configured in my KMail. I actually saw this bug in the "Check if dup" list, but since this involves IMAP and my case does not, I did not think this was the same bug. Further, a first look at the backtrace here and in the three other bugs shows a distinct difference halfway through the trace. Here, QEventLoop::enterLoop () is called by QEventLoop::exec () but in the other three, it is called by QApplication::enter_loop (). After that, there are many more differences. So I really do not know if this bug and the other three are the same. Yeah, my report bug 129231 seems to be the same with bug 128560 and 130010, and my configurations have nothing about IMAP too. I tried to delete every cache as possible, including my full-text index, and something that "seems to be of no use" but in vain. I don't think this (128560, 129231 & 130010) is the same bug with this one. The bug I am seeing is definitely related to IMAP. If I blow away ~/.kde/share/apps/kmail/imap/nnnnnnn where nnnnnnn varies and is apparently the cache file, it all works again. To do so, I log out, log back in under Gnome (or could use a non-Graphical login), kill off all the "kontact" programs that are running (there are at least 3 or 4) then delete the file. My experience was if I tried to delete this file while KDE is running, it is re-created in a broken state when KDE exists, and so the problem persists when KDE restarts. The only "downside" to fixing the problem this way is that the cache is lost, so if you have some big IMAP files as I do (one is 3GB) it takes a bit to reload the cache the first time. *** Bug 131368 has been marked as a duplicate of this bug. *** Hi, Just thought I'd mention that in Bug 131368 which was marked dupe of this one, I am not using IMAP at all. It's all POP3 and maildir for storage on local disks. *** Bug 138710 has been marked as a duplicate of this bug. *** The bug contains too much 113329 related noise. So let's start from scratch with that other bug :) *** This bug has been marked as a duplicate of 140460 *** |