Bug 317315

Summary:	kmail2 doesn't seem to do proper multi-threading
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Ruchir Brahmbhatt <ruchir.brahmbhatt>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	GIT (master)
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ruchir Brahmbhatt 2013-03-25 08:21:43 UTC

OS: opensuse 12.3 x86_64
KDE: 4.10.1 from KDE:Release repository
Account: Gmail IMAP with disconnected mode

Finally I started using kmail2 as everyday mail client. It is so intuitive and fast. However still there are some problems making it less efficient at times. For example when it is checking all folders(I have lots of them) on a large mailbox, when you want to refresh inbox, its not possible. Right click and update folder or hitting F5 has no effect. Must wait for this process to finish and then only any folder can be refreshed. Same way refreshing calendar(I have google calendar configured) is also not possible while this process is going on. Seems like it does mail checking in single thread only and not performing any other action user performs and probably queuing it. I think action performed by user like refreshing particular mail folder or calendar should be done in parallel so user doesn't have to wait for long action to finish.

Reproducible: Always

Steps to Reproduce:
1. Have a large imap inbox configured.
2. On startup, kmail2 will start mail checking and downloading all mails(as disconnected mode enabled)
3. Try to refresh inbox any other folder or calendar manually.
Actual Results:  
No response on action till mail checking procedure finishes.

Expected Results:  
Action performed by user should get equal priority and should be executed immediately.

Comment 1 Denis Kurz 2016-09-24 20:37:26 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 2 Denis Kurz 2017-01-07 22:07:41 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.