I've chosen the layout to display an email once I click on it in the message list. Sometimes the whole GUI freezes for about 10 seconds before the email is diplayed. This includes open composer windows. The akonadi new-mail notification windows does not freeze. Stopping kmail, akonadi and killing all processes matching kde*, including the mysql database does not seem to help. It semt to help the other day though. Reproducible: Sometimes Steps to Reproduce: Sorry I can't figure out how to reproduce it. During freeze there's no output in the terminal from which I started akonadi and mail. Right after the freeze I see these messages: SEARCH: Query: "{ "limit" : -1, "negated" : false, "rel" : 1, "subTerms" : [ { "cond" : 0, "key" : "email", "negated" : false, "value" : "nico.schlitter@kit.edu" } ] }" MimeTypes: ("text/directory") Collections: QVector(652, 660, 678, 678, 652, 658, 659, 658, 659, 660) Remote: false Recursive true Executing search "kmail2-701319238-SearchSession" Search done "kmail2-701319238-SearchSession" (without remote search) Result: 3 matches SEARCH: Query: "{ "limit" : -1, "negated" : false, "rel" : 1, "subTerms" : [ { "cond" : 0, "key" : "email", "negated" : false, "value" : "evelina.buttitta@kit.edu" } ] }" MimeTypes: ("text/directory") Collections: QVector(652, 660, 678, 678, 652, 658, 659, 658, 659, 660) Remote: false Recursive true Executing search "kmail2-701319238-SearchSession" Search done "kmail2-701319238-SearchSession" (without remote search) Result: 0 matches SEARCH: Query: "{ "limit" : -1, "negated" : false, "rel" : 1, "subTerms" : [ { "cond" : 0, "key" : "email", "negated" : false, "value" : "evelina.buttitta@kit.edu" } ] }" MimeTypes: ("text/directory") Collections: QVector(652, 660, 678, 678, 652, 658, 659, 658, 659, 660) Remote: false Recursive true Executing search "kmail2-701319238-SearchSession" Search done "kmail2-701319238-SearchSession" (without remote search) Result: 0 matches
Not sure, but I think I managed to mitigate this by removing unavailable mountpoints from /etc/fstab. It seems that (just like the file dialogue) checks all entries in fstab -- and depending on the network one is in cannot reach them and runs into a timeout. Therefore, I suggest network sharesto be checked in a background thread.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.