Bug 341974 - akonadi keeps synchronizing the same folder again and again consuming cpu
Summary: akonadi keeps synchronizing the same folder again and again consuming cpu
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 1.13.0
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-17 15:45 UTC by Michał Walenciak
Modified: 2017-01-07 22:37 UTC (History)
3 users (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 Michał Walenciak 2014-12-17 15:45:47 UTC 
Hi

My akonadi server seems to have problems with one particular directory in my imap account.
This is a "all mails" on gmail account (not sure about english name of this folder).
In my case I have there thousands of emails.
It goes to ~60-80%, then stops and starts again.

When it stops I can see errors in status bar like: "Unable to fetch item from backend".

Until akonadi hangs on this folder everything looks ok - i can read and send emails.
When it stops for the first time - kmail becomes useless - I cannot read any email.

Reproducible: Always
Comment 1 Michał Walenciak 2014-12-17 16:37:52 UTC 
exact error message from status bar:
"Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Comment 2 Denis Kurz 2016-09-24 20:41: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:37:21 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.