Bug 326521 - Message / next message is displayed in preview window only after some time (5 to 10 minutes)
Summary: Message / next message is displayed in preview window only after some time (5...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.11.2
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-23 17:58 UTC by Thomas Arend
Modified: 2017-01-07 21:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Arend 2013-10-23 17:58:49 UTC
Preview window shows "Inhalt des Ordners wird abgeholt. Bitte warten ..." it take some minutes before the first message is shown in the preview window.

When selecting the next message it takes another 5 to 10 minutes to display the message.  

Reproducible: Always

Steps to Reproduce:
1. Start kmail2.
2. Select a folder and a message
3. Wait 5 to 10 minutes until the message is displayed
4. kontact, mysqld and akonadi use ~ 50% and more CPU on a 6 core with 8 GByte system. all the time
Actual Results:  
Only the message list is displayed. 

Expected Results:  
* I would expect that a message is displayed immediately after I select a message. 
* There is no need to read the whole folder.
* In 5 Minutes it should be possible to scan all my messages some thousand times.
* I would expect that the kontact, mysqld and akonadi only use a reasonable amount of CPU when kontact runs in the background.
Comment 1 Denis Kurz 2016-09-24 18:21:32 UTC
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.
Comment 2 Denis Kurz 2017-01-07 21:58:04 UTC
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.