Summary: | Kmail takes several minutes (and more) to open a message | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | peterterpstra <peterterpstra> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | grave | CC: | cfeck, ewoerner |
Priority: | NOR | ||
Version: | 4.11.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Waiting for message to open, which takes several minutes or dies not happen at all.
Also this takes ages... Sending a message... Top: kmail, akonadiserver and mysqld take lots of CPU |
Description
peterterpstra@versatel.nl
2013-09-18 08:26:04 UTC
Created attachment 83019 [details]
Waiting for message to open, which takes several minutes or dies not happen at all.
Would like to add some more images, but don't see a possibility.
Thank you kindly for your efforts
Created attachment 83021 [details]
Also this takes ages...
Created attachment 83022 [details]
Sending a message...
Created attachment 83024 [details]
Top: kmail, akonadiserver and mysqld take lots of CPU
In my case, the underlying cause was a duplicate inbox folder, as described in bug #322958. Peter: could you please check whether you have a duplicate special folder as well? Sorry for being so late to read your comment! NO no double folder here. Since a few weeks after one of the updates i can say that the reported problems do not exists anymore. Kmail is very usable now. Because i was using mutt i did not noticed the bugfix, Happy to have kmail back working again. Thank you so much for all the efforts that have been done! Also a Happy 2014 for all! Peter This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |