Kmail often stuck at "Retrieving folder contents..."

[Tim Ruehsen]

Please wait...

No matter how long I wait, KMail is stuck.
I have to restart KMail.

My impression: It happens regular when changing folders too fast.

Of course I tried akonadictl (fsck + vacuum + restart) with no success.

Any idea where to look at or what to do ?

Regards, Tim

[Martin Steigerwald]

Hello Tim.

This topic has been discussed just recently on kdepim-users mailing list. It
appears to be a known issue.

Please review

"Retrieving Folders..." hang and a possible solution

thread there.

https://mail.kde.org/mailman/listinfo/kdepim-users

Thanks,
--
Martin

[David Baron]

Select the option to download for off-line use. Once the stuff is there,
problem will not recur.

I was under the impression there were problems on GMail servers but apparently
more widespread.

[Tim Ruehsen]

Thanks Martin,

I tried to increase the INNODB buffer as suggested with no success.
And btw, I do not have a performance problem, KMail is hanging forever.

Someone mentioned
https://cgit.kde.org/akonadi.git/commit/?h=Applications/
16.12&id=d42f94701f38c26cf3439727b50ee73cf0d09bee

Not sure how fast it will make it into Debian.
And I am not sure if this addresses my problem... I now have several emails
that produce the issue just by clicking on them.

KMail evolved from a once very stable and fast mail client to a almost
unusable one. Each iteration/bugfix comes with new bugs that are even worse
than the ones fixed. My conclusion after years of suffering: KMail does not
have enough dev resources - it is literally dead and meanwhile lacks many
features that other mail client had for years (one badly missing and requested
years ago: Saving encrypted messages unencrypted locally).

Tim (really frustrated at the moment)

[solitone]

On Wednesday, 1 March 2017 11:17:56 CET Martin Steigerwald wrote:
> This topic has been discussed just recently on kdepim-users mailing list.

I also have innodb_buffer_pool_size set to 80M in ~/.local/share/akonadi/
mysql.conf--rather than the suggested/default 128M value. Is 80M debian
specific? I never changed that value, it's what I have since intallation.

Regards,
Davide

[solitone]

On Friday, 3 March 2017 16:40:25 CET solitone wrote:
> I also have innodb_buffer_pool_size set to 80M in ~/.local/share/akonadi/
> mysql.conf--rather than the suggested/default 128M value. Is 80M debian
> specific? I never changed that value, it's what I have since intallation.

Ooops, I gather that 80M is akonadi default--not debian. While 128M is mysql
default.