Bug 345979 - kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
Summary: kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
Status: CONFIRMED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.11.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-08 11:34 UTC by Christo
Modified: 2019-07-10 12:37 UTC (History)
5 users (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 Christo 2015-04-08 11:34:14 UTC
i have several google-akonadi-ressources .. all offline-imap

the biggest one (~6GB) keeps getting stuck on a ragular basis .. it doesnt retrieve imap-email anymore then .. at akonadiconsole the status then show "Verbindung aufgebaut" (="connection established") .. but it stays stuck there .. .. this doenst change over the hours

only if i do a 'akonadictl restart' its starting again ... but after a while (a hour or less) - stuck again 

i check at akonadiconsole for errors but couldnt spot any ... 

if someone can tell me how top find relevant akonadi-errors - i'd be glad to provide more info 

kde 4.14.6
Akonadi 1.13.0

Reproducible: Always

Steps to Reproduce:
i have no idea how to reproduce this -- simply happens

Actual Results:  
offime-gmail-imap-ressource gets stuck after establishing connection

Expected Results:  
sync and idle
Comment 1 Robert Fries 2015-05-28 19:20:15 UTC
I am having the same experience using F21 akonadi-1.13.0-2.fc21.x86_64.  My connection is to the imap port on an exchange server.  I know I have a path to the server as using konqueror to access imaps://<userName>@<server> works and will display a directory with messages.  I have been able to clear this in the past doing incantations such as "akondictl stop" followed by "akonadictl start" but that only works sometimes and I have not made any association as to why it sometimes corrects the situation.  The correction does not seem to last long.  This machine is a laptop so the server is frequently not available and the machine goes through frequent suspend/resume cycles.  But I don't know that that is the trigger.  Any suggestions for things to look at when this happens ?
Comment 2 Denis Kurz 2017-06-23 20:03:08 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 silentz0r 2017-09-17 15:30:43 UTC
(In reply to Denis Kurz from comment #2)
> 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.

This bug stills exists. I'm on whatever version is currently on Arch Linux's upstream repositories which is fairly up-to-date. This does not even happen for such large collections, I've had this happen on my work mail which is less than 400MB (0.33 GB (2%) of 15 GB used, per gmail's quota).

This is not an old migrated setup either, the PC was wiped clean less than 6 months ago and everything was reinstalled.

I've noticed that one specific folder which contains over 1,000 emails is the one that gets stuck when syncing. After restarting akonadi manually (akonadictl restart) and hitting the sync button, Kmail starts syncing my folders one by one and eventually gets to the large folder, which only goes up to 84% IIRC. Maybe this helps track down some resource which would crash on anything above 800-900 emails (84% of 1100) or maybe it's just an unrelated visual while akonadi crashes.

This seems like akonadi hangs when any task gets stuck, which is pretty bad. It has also been confirmed by a KDE dev on the forums: https://forum.kde.org/viewtopic.php?f=215&t=139394#p375588
Comment 4 Christoph Feck 2017-10-04 15:14:14 UTC
Thanks for the update; changing status.
Comment 5 Tom Kijas 2019-07-10 11:48:09 UTC
I have same experience for months and THANK YOU for workaround - akonadictl restart in konsole.

I use latest KDE NEON (Ubuntu based) User edition
KMail 5.11.2
KDE Frameworks 5.59.0
Qt 5.12.3

regularly the akonadi dies and emails stays in Outgoing folder forever.
Comment 6 avlas 2019-07-10 12:37:06 UTC
This happens to me (in KDE neon) most of the times after "Accepting a Google Calendar Invitation Request" in my gmail account.

The email that is sent (not always but very frequently, I would say 80% of the times or more) gets stuck and then no more emails can be sent from any account (gmail and others).

Saying because if you could reproduce this behavior, it may help to debug and fix the issue.

[Note: I have the feeling that this happens more frequently if the akonadi process has been running for a while]