Version: SVN trunk (KDE 4) (using Devel) OS: Linux After I fixed bug #250747 - https://bugs.kde.org/show_bug.cgi?id=250747 , with a lot of help form piggz on IRC, and set up the local folders, then KMail is spending many hours "syncing collections" of the different folders, several times for each folder (why?). Furthermore, it marks all the messages in all the folders as unread, despite the fact they had read flags in their headers set by KMail 1. I don't understand what this "syncing" means, but I know that it communicates with the Akonadi PostgreSQL backend and slowly fills up my /-partition. I still cannot properly use KMail despite having quit it and started it again. Why can't the KDE 4 people stop messing things up? Reproducible: Didn't try
OK, I've built the kdepimlibs4-trunk and kdepim4-trunk in a vein attempt to fix this problem. However, now kmail is very slow, very buggy and practically unusable: 1. It takes forever to switch to a folder, even if the folder contains very few messages. 2. Marking an entire folder as already read (keywords "mark as read", read, unread, message) does not update the folder view in time. 3. After right-clicking the mouse button on a folder in the folder tree, it takes forever for the context menu to appear. 4. KMail consumes a lot of CPU and 11.6% (!) of my 2.5 GB RAM. Akonadi consumes 13.7% RAM (!!). 5. Some messages which I select in the message pane are still marked as unread after I move to a different message. They should be marked as unread. 6. KMail does not report why it is so slow and unusable and there is no progress indication. ---------------- I cannot believe none of you noticed how much unusable KMail is right now in the trunk. I've been unable to check and respond to my email for a few days now, and I can thank you people for it. Bravo! Regards, -- Shlomi Fish
Does this still exists with KMail/Akonadi 4.6 beta 5? Can you retest and check if this is still valid? There have been MASSIVE bugfixings there.
(In reply to comment #2) > Does this still exists with KMail/Akonadi 4.6 beta 5? Can you retest and check > if this is still valid? There have been MASSIVE bugfixings there. I am no longer able to reproduce this because KMail on Mandriva Cooker is no longer KMail2 but rather has been downgraded to Version 1.13.7. See: http://forum.mandriva.com/en/viewtopic.php?f=35&t=134876 I don't blame the Mandriva packagers for downgrading it, because frankly with Akonadi and Nepomuk and all these curse words, KMail2 has become extremely buggy and unreliable. I don't know what to do about this bug - it may still exist, but I'm not in the mood to build the new KDEPIM just to test it on this system. Regards, -- Shlomi Fish
yes, I am able to reproduce with master from yesterday; my laptop has been "syncing" for several hours and, despite all mail is already there, akonadiserver and dbus-daemon still eat up to 100% cpu for no apparent reason.
Shlomi, Jacopo, thanks for reporting, confirming your issue. It is related to an ancient version of KMail which uses Nepomuk. As KMail 4.14 doesn´t use Nepomuk anymore and has received some maildir indexing performance fixes, I think it is likely that the original issue you reported here is fixed. Thus I set to resolved/unmaintained. In case you still see the original issue with KMail from KDEPIM 4.14 and Akonadi 1.13 please tell so, and I will reopen the bug. Also Shlomi, you reported a lot of different issues in comment #1. In case you can reproduce any of these still please check whether they are already reported. Add your finding to an existing bug reporting or create a new one. I will treat this bug report as just the original issue you reported. Please always file one bug per issue you find and also check for duplicates. Thanks, Martin