Re: Akonadi DB Errors, "Trash" sync hangs forever
Ingo Klöcker <[email protected]>
| Newsgroups | gmane.comp.kde.devel.pim,gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <2485594.EzT29qfnlD@thufir> |
On Samstag, 20. Oktober 2018 02:49:30 CEST Boyd Stephen Smith Jr. wrote: > I'm not 100% sure this is the right place to ask for help. The right place would have been the kdepim-users mailing list (where I'm sending my reply to, with kde-pim as CC; please send further replies to the kdepim-users mailing list only). On the kdepim-users mailing list there is a nice little community of helpful KMail users. > I have an Akonadi IMAP resource accessing my own dovecot server, and the > first sync works great. However, later synchronizations hang on the "Trash > folder". I can't stop the synchronization once it is hung by using the > cancel button in the kontact/kmail task list. If the problem only occurs for the Trash folder, then I suggest to disable automatic synchronization of this folder (under Retrieval in the folder properties). > This prevents new mail from showing up, until I restart Akonadi (restarting > kmail/kontact doesn't help), and effectively force a synchronization to > restart with INBOX. > > Console messages pasted here: > https://www.reddit.com/r/debian/comments/957r7r/ akonadi_postgresql_buster/ > > Should I open a bug? You seem to be using a rather old version of KMail (version 5.2.3 according to the header of your email). The current version is (at least) 5.9.1. There have been a lot of bugfixes and improvements since 5.2.3. If easily possible, then you should update to a newer version of KMail. If the problem still occurs with an up-to-date version of KMail, then opening a bug report makes sense. > Is there a better recovery method in the meantime? Am I doing something > wrong? It's always helpful to tell the mailing list which version of KMail (and Akonadi) you are using. > Deleting and re-creating the resource seems to make synchronization work for > a little while, but in less than 72 hours, I get a hang with the same > symptoms and very similar messages. Regards, Ingo
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRxKgkQMhrHYtSAVAgadH5FMOC52AUCW8yV2QAKCRAadH5FMOC5 2CGCAJ9XIk94/Y2oTtIM6j1HGWPVS6W2ogCfc0+P4fc3AOMb+b7tKzMh3zvc4Nw= =QKcB -----END PGP SIGNATURE-----