Bug 320099

Summary: KMail shows progress for "Ready" and "Off-line" states of accounts
Product: [Applications] kmail2 Reporter: Thiago Macieira <thiago>
Component: UIAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: Git (master)   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: screenshot of the problem

Description Thiago Macieira 2013-05-21 15:24:41 UTC 
[This might be an Akonadi bug]

Sometimes, when I get disconnected from the Internet (usually by suspending while connected and resuming without network, but by other means too), the Akonadi IMAP accounts go into a "Ready" or "Off-line" state, but KMail still shows them as in-progress of something. The slider showing that it's checking the accounts is moving.

Needless to say, the animation is pointless, misleading and wastes battery life. Please do not show in-progress of a state that isn't in progress.

Reproducible: Sometimes

Steps to Reproduce:
Unable to provide specific instructions to reproduce.
Actual Results:  
The slider showing progress is active, indicating that Akonadi is doing something, even if all accounts are "Off-line". See also the attached screenshot for the case of "Ready" and "Off-line".

Expected Results:  
If all accounts are off-line, then no progress should be shown and the slider animation should not be active. Most of the time, it works like that.
Comment 1 Thiago Macieira 2013-05-21 15:25:13 UTC 
Created attachment 79997 [details]
screenshot of the problem
Comment 2 Laurent Montel 2013-05-21 15:31:17 UTC 
Ok will investigate it.
Comment 3 Denis Kurz 2016-09-24 18:08:23 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 4 Denis Kurz 2017-01-07 22:44:38 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.