Bug 305896 - Akonadi-4.8.3 message that "Unable to fetch item from backend" is uninformative
Summary: Akonadi-4.8.3 message that "Unable to fetch item from backend" is uninformative
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.8
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-27 19:01 UTC by Christian
Modified: 2017-01-07 22:45 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 Christian 2012-08-27 19:01:24 UTC
Sometimes I get this kind of message popup on my screen. Usually it indicates an application name (e.g. Plasma-Workspace-Environment, or KOrganizer-Service) and the error message "Unable to fetch item from backend".
Occasionally there are also numbers such as Resource -32, item 1.
This type of message is useless to me.

Reproducible: Always

Steps to Reproduce:
1. Read the popup message
Actual Results:  
Uninformative text.

Expected Results:  
It should say at the minimum:
a) What resource is supposed to be fetched.
b) Why it doesn't succeed - does it not exist? is it locked? is the query malformed?
c) What is the context of this error, i.e. as a consequence of this message, what part of my system is going to have a problem?
Comment 1 Dennis Schridde 2012-10-04 23:04:30 UTC
I agree with the original reporter. Would be much easier to figure out what is going on, if the message would contain more information.
Comment 2 Denis Kurz 2016-09-24 20:36:12 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:45:02 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.