I've been using KDE since the beginning over a decade ago and finally had to migrate to the kmail/akonadi/nepomuk combo. The migration itself was a disaster which I mostly expected after googling around even after delaying migrating for so long. I finally got everything mostly working and now kmail seems to sync folders way to often. If I click on my Inbox folder with about 13000 messages, it takes a long time to sync then the message list finally shows up. If I then click on another folder and do something else for 10-15 minutes, when I click on Inbox again the eternal syncing starts again. I put binlog_format=row in my mysql.conf and i've deleted/rebuit the akonadi and nepomuk databases more times than I can count. How about considering: 1. Skipping akonadi/nepomuk for email. It's great for calendar/contacts/alarms/etc but for e-mail it just doesn't seem a good fit at all. Even searching is easier without slowing things down even more with nepomuk indexing, and i'm talking about using grep to search mail folders then using kmail just to read the message. or 2. Adding a date criteria for syncing so subsequent syncs only sync for new items since the last sync. There's gotta be a way to make kmail2 usable with large mailboxes. Right now i'm finding it just barely serviceable. Reproducible: Always Steps to Reproduce: 1. Open kmail or kontact and click on mail 2. Click on a folder with thousands (10k) messages 3. Click on another folder 4. Go away for about 15 minutes 5. Click on first folder again Actual Results: Long pause while it syncs Expected Results: Same as previous kmail behaviour, click on a folder and the message list shows up either immediately or after a couple of seconds. I'm a big fan of KDE and find it to be a fantastic desktop, but email in this recent version is a nightmare. This really needs to be fixed/optimized somehow because email is one of those show-stopping critical parts of an operating system. Seems maybe KDE is getting a little to fancy and adding complexities that are causing nothing but problems for the vast majority of users (based on the huge number of results for researching kmail/akonadi/nepomuk problems on google)
Bug was moved from kmail2 to akonadi, so i updated it to specify akonadi version 1.8.1 (1.8.1-1.fc17 x86_64 from Fedora 17 RPMs). Upgrade was from a Fedora 14 system to a Fedora 17 system. Not sure if this belongs in Akonadi because the best approach may be to dump akonadi/nepomuk altogether for email in kmail2.
> best approach may be to dump akonadi/nepomuk altogether for email in kmail2 If you want kmail to not use akonadi, simply use the 4.4 version (using it myself), until the issues are resolved. You can compile 4.4 pim and pim-runtime with 4.9 pimlibs, but please understand that this is not an officially supported combination.
Man do I ever wish I did that before wading into the migration! Seems disabling "Synchronize when selecting this folder" makes kmail much more usable. Not sure if there's any side-effects and it'll probably still take forever when it does sync but with that option disabled I can select folders and my messages show without the rubberiness. From akonadiconsole (or the kmail folder list if you're real patient): - Select the the brower tab - Right click on kmail folders and select the "Folder Properties" item - Hit the Retrieval tab - Uncheck "Synchronize when selecting this folder" - Also have to uncheck "Use options from parent" if it's checked. Worked for me but no idea if there's any nasty side effects waiting...
So after a few days disabling the synchronize option seems to make mail usable again. The catch is you have to disable it from within kmail because setting it in akonadi doesn't stick (it resets automatically). So far the only side effect is I get the "Resource KMail Folders is broken" message more often now but that's an accurate message because "Resource KMail Folders" is most definitely broken, but hopefully not broken beyond repair! Stubbornly sticking with kmail for a bit longer yet...
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Performance has been improved, and we are not gonna rewrite akonadi