Bug 344951 - showJobError: There is no GUI delegate set for a kjob, and it failed with error: "ItemRetrieverException: Unable to retrieve items"
Summary: showJobError: There is no GUI delegate set for a kjob, and it failed with err...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.14.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-08 11:50 UTC by BRULE Herman
Modified: 2018-01-31 16:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2015-03-08 11:50:30 UTC 
Hello, I have 15000 mails to remove, and delete all do:
showJobError: There is no GUI delegate set for a kjob, and it failed with error: "ItemRetrieverException: Unable to retrieve items"
For the KDE update 4.12 -> 4.14 I have change the akonadi backend, the manual remove of the mails received after this date work, but don't work before this date.
Cheers,

Reproducible: Always
Comment 1 Laurent Montel 2015-03-09 13:07:14 UTC 
As Nicolas reported me, you changed your backend as sqlite.
It's not really a good idea see: https://techbase.kde.org/Projects/PIM/Akonadi/Database#Sqlite

You will have a lot of problem.
I will search more information about sqlite support and see if I can find something.
Comment 2 Denis Kurz 2017-06-23 19:56:56 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 16:52:28 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.