Version: 1.13.6 (using KDE 4.6.0) OS: Linux this happens to me every time with KMail 1.13.6 and KDE 4.6.0 built from source on Gentoo Linux. i am trying to access the inbox of my Gmail account. kmail loads a few dozen messages, whereupon i see a bunch of messages in the console like this: --- kmail(25926)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x2ba1990) kmail(25926) KMFolderImap::slotListFolderResult: "INBOX" download KUrl("imaps://{username}@imap.gmail.com:993/INBOX/;UID={list of UIDs};SECTION=ENVELOPE") kmail(25926)/kio (Scheduler) KIO::SchedulerPrivate::assignJobToSlave: KIO::Slave(0x9a3280) KIO::TransferJob(0x2ba1990) --- then i get an error dialog that says "The process for the imaps://imap.gmail.com protocol died unexpectedly.", and in the console i see this: --- kmail(25926)/kio (Slave) KIO::Slave::kill: killing slave pid 25980 ( "imaps://imap.gmail.com" ) kmail(25926) KMFolderImap::getMessagesResult: KIO::TransferJob(0x12c1ad0) 143 false kmail(25926)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::instance: instance(): ... initialised kmail(25926)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readConfig: readConfig(): local zone= "EST5EDT" kmail(25926)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readZoneTab: readZoneTab( "/usr/share/zoneinfo/zone.tab" ) kmail(25926) MessageList::Core::View::resizeEvent: Resize event enter (viewport width is 0 ) kmail(25926) MessageList::Core::View::resizeEvent: Resize event enter (viewport width is 0 ) kmail(25926) MessageList::Core::Widget::Private::checkSortOrder: Could not restore sort order for folder ".1036205189.directory/INBOX" kmail(25926) KMail::NetworkAccount::setCheckingMail: connections to server "imap.gmail.com" now 0 kmail(25926) KMail::AccountManager::processNextCheck: processNextCheck, remaining 0 kmail(25926) KMail::AccountManager::processNextCheck: account "Gmail" finished check kmail(25926) MessageList::Core::View::resizeEvent: Resize event enter (viewport width is 620 ) kmail(25926) MessageList::Core::View::resizeEvent: Resize event enter (viewport width is 620 ) kmail(25926) MessageList::Core::View::resizeEvent: Resize event enter (viewport width is 620 ) kmail(25926)/kdeui (KNotification) KNotificationManager::notificationClosed: 1006 --- every time kmail tries to fetch all of the messages in my inbox, it gets a little farther, but soon hits the same error. i can view the messages that do get retrieved without any apparent issues. i haven't found a workaround. i tried ``rm -r ~/.kde4/share/apps/kmail/``, and i tried doing a full rebuild (from source, without ccache) of all of my Gentoo packages. Reproducible: Always possible duplicate: bug 125041
this bug disappeared from my system. after the last time i verified it as reproducible, i performed the following possibly relevant steps. note that most of these are Gentoo-specific. 1. rescue my somewhat broken installation of GCC 4.5 + Graphite (broken in that it causes ICEs at seemingly random times when building various packages, including GCC itself). 1. disable Graphite loop optimizations in CFLAGS in /etc/make.conf. 3. # USE=-gtk emerge sys-devel/gcc:4.4 5. # gcc-config x86_64-pc-linux-gnu-4.4.5 4. # USE=-gtk emerge -e system 6. # USE=-gtk emerge sys-devel/gcc:4.5 5. # gcc-config x86_64-pc-linux-gnu-4.5.2 7. # emerge -e gtk+ 8. # emerge gcc 2. do a total rebuild of my packages now that GCC is somewhat sane. 1. # emerge -e system 2. # emerge -e world 3. update and upgrade packages, including KDE 4.6.0 -> 4.6.1. 1. # emerge --sync 2. # emerge -uND world without knowing the real source of this problem, i'm guessing it could've been any of the following: * a bug that got fixed in KDE 4.6.1. * KMail or one of its libraries doesn't support GCC 4.5 + Graphite. i say GCC 4.5 because this bug wasn't present on the same system with GCC 4.4 + Graphite. then again, given the apparently insane nature of GCC 4.5 + Graphite in general, it's probably not fair to blame it on KMail. * undefined behavior caused by a reverse dependency rebuild requirement that, for whatever reason, didn't get caught by past runs of revdep-rebuild, but naturally got caught by ``emerge -e``. but usually these manifest as "cannot load shared object [...]" when launching, not as buggy runtime behavior.