Bug 351993 - kmail seems to hang infinitely long on retrieving emails
Summary: kmail seems to hang infinitely long on retrieving emails
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-08-29 20:02 UTC by Elmar Stellnberger (AT/K)
Modified: 2018-10-28 03:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
akonadi selftest report returrned on restarting the akonadi server (4.17 KB, text/plain)
2015-08-29 21:23 UTC, Elmar Stellnberger (AT/K)
Details
job tracker: gmail inbox hangs at 32% (353.69 KB, text/plain)
2015-08-29 21:33 UTC, Elmar Stellnberger (AT/K)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2015-08-29 20:02:56 UTC
After successfully registering several email accounts (yahoo, gmail, revido) kmail has retrieved the IMAP directory structure successfully but it fails to download even a singleton mail. It seems to hang forever the progress bar moving from the left to the right and back again.

Reproducible: Always
Comment 1 Elmar Stellnberger (AT/K) 2015-08-29 20:39:50 UTC
starting akonadi-console and viewing the task list yields the following for yahoo mail:

ResourceScheduler: Online
 current task: 6 SyncAll 
 queue 0 is empty
 queue 1 is empty
 queue 2 is empty
 queue 3 is empty
 queue 4 1 tasks:
  26 SyncCollectionTree 

IMAP tasks:
Comment 2 Elmar Stellnberger (AT/K) 2015-08-29 21:09:17 UTC
Switching a task on/offline or abort/restart acticvity does not help.
However a full aconadictl restart refreshes the system.
Then it downloads some messages for some time until it gets stuck again.
Comment 3 Elmar Stellnberger (AT/K) 2015-08-29 21:11:19 UTC
kmail version 4.81.beta1
Comment 4 Elmar Stellnberger (AT/K) 2015-08-29 21:23:56 UTC
Created attachment 94277 [details]
akonadi selftest report returrned on restarting the akonadi server
Comment 5 Elmar Stellnberger (AT/K) 2015-08-29 21:33:02 UTC
Created attachment 94278 [details]
job tracker: gmail inbox hangs at 32%
Comment 6 Elmar Stellnberger (AT/K) 2015-08-29 21:43:10 UTC
It may likely be that it gets stuck as soon as it tries to download a second folder in parallel.
Comment 7 Tim Climis 2015-09-19 01:29:54 UTC
I had this problem but only with new folders.  I created some new folders at work on an existing account - then moved mail into them.  Came home, folders were empty.  Existing folders loaded new mail just fine (although, they wouldn't refresh until I canceled the attempt to load mail into the new folders)

In an attempt to get things to reset, I removed the account, and readded it.  Now I have no mail at all.
Comment 8 Martin Kostolný 2015-09-23 14:15:47 UTC
I have the same problem. Because I recently started to have problems with old IMAP accounts in akonadi mysql database (it started to crash the mysqld process hence akonadi was unable to read the mail data) I decided to remove all akonadi configuration and data and start over.

I've added first IMAP account and everything synchronized OK (it was zoho mail). After adding the second one it only synchronized empty folder structure and hanged indefinitely while synchronizing. The synchroniziation hanging is always accompanied with sending and receiving the same amount of data simultaneously (I can see that in Network Monitor).

I've also tested that this second IMAP account behaves the same with clean - empty user, being the only mail account created. This IMAP account is related to my work (so it's not gmail or something) but it always worked with past KMail versions. Also note that basic synchronization still works - e.g. if I create a mail in empty "Drafts" folder on the remote server -> it gets synchronized in kmail. But "Sent" and "Inbox" (the only folders filled with a lot of e-mails) are causing the hanging and do not pull in a single e-mail.

I cannot say when this behaviour started. It was there probably since KDE Applications 15.08 but I guess the simple synchronizations still works so the full synchronization was not performed.

I was testing with Plasma 5.4.1, KF 5.14.0, KDE Applications 15.08.1, KMail version 5.0.1.
"akonadictl --version" prints out: Akonadi 5.0.51
I have Arch Linux.
Comment 9 Denis Kurz 2017-06-23 20:20:59 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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 10 Tim Climis 2017-06-24 12:27:17 UTC
I can confirm that I have not had this problem with any recent version for at least a year.
Comment 11 Andrew Crouthamel 2018-09-28 02:35:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Andrew Crouthamel 2018-10-28 03:36:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!