(evolution:8197): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
The first issue you report has been already reported as a Webkit-bug as far I can tell - It appears to be already solved and there is a patch availabel at
But it shouldn't be causing any issue with email fetching, following that thread:
While loading email into WebView in Evolution with WK1 it's showing
this warning. Everything loads and renders fine. I'm on
(evolution:21890): GLib-GObject-CRITICAL **: g_closure_unref:
assertion 'closure->ref_count > 0' failed
(evolution:8197): camel-imapx-CRITICAL **: imapx_untagged_fetch: assertion 'found' failed [imapx:A] Data read failed with error 'unexpected server response:' [imapx:A] I/O: '' [imapx:A] Ignoring timeout error, nothing was waiting (original error: Socket I/O timed out)
The second one suggests evolution is unable to fetch a certain message from the server and I had a similar problem in the past which was caused by the fact that Gmail does not really delete emails from the server under certain circumstances:
If you delete a message from your inbox or one of your custom folders
in your IMAP client, it will still appear in [Gmail]/All Mail.
Here's why: in most folders, deleting a message simply removes that
folder's label from the message, including the label identifying the
message as being in your inbox. [Gmail]/All Mail shows all of your
messages, whether or not they have labels attached to them. If you
want to delete a message from all folders, move it to the
Accordingly, Evolution tries to fetch a message which actually does not exist in the specified location/folder, thus receiving an unexpected server response from the server.
Anyway, the problem was solved by deleting the file
which in essence should be the same as DELETING THE EMAIL ACCOUNT.
I'd strongly suggest to do that after backing everything up. If you already deleted the account and created it again, delete the folders.db file manually (with evolution closed) and start evolution again. It should then rebuild the folder structure and information from the server for all accounts.