Bug 309224

Summary: When ItemFetchJob fails, there is no visible error but the wheel spins forever
Product: [Frameworks and Libraries] Akonadi Reporter: Thiago Macieira <thiago>
Component: libakonadiAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: GIT (master)   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Akonadi Console job tracker showing the error.

Description Thiago Macieira 2012-10-29 22:37:41 UTC 
When I enter a given folder that causes an Akonadi::ItemFetchJob to fail, the "spinning wheel" distraction that replaces the folder icon will spin forever. This happens in both Akonadi Console and in KMail.

The ItemFetchJob error was "Unable to fetch item from backend (collection 85, resource -1)", but I'd argue that it's irrelevant what the error was.

The point is that there was an error and, though the user may be unable to do anything to correct it, there should be a visible indication of that, including possibly information to be transmitted to the developers to aid in fixing that particular error. As it stands, the wheel spins forever, as if KMail or Akonadi Console were waiting for something to happen.

Reproducible: Sometimes

Steps to Reproduce:
1. Enter, for the first time, a folder that produces a fetch error
2. Note that the folder icon is replaced by the spinning wheel
Actual Results:  
The wheel remains spinning forever. No error message is shown, ever.

Expected Results:  
An error message should be displayed as soon as the fetch error was noticed.
Comment 1 Thiago Macieira 2012-10-29 22:39:05 UTC 
Created attachment 74872 [details]
Akonadi Console job tracker showing the error.
Comment 2 Denis Kurz 2016-09-24 20:44:03 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 3 Denis Kurz 2017-01-07 22:02:34 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.