Re: [Evolution] SEGV in evolution 3.36.3

[Milan Crha <mcrha redhat com>]

On Thu, 2020-06-04 at 09:14 +0200, Joakim Tjernlund via evolution-list
wrote:
#7  0x00007fa9a0716445 in camel_folder_summary_remove_uid ()
    at /usr/lib64/libcamel-1.2.so.62
#8  0x00007fa990e984d1 in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#9  0x00007fa990e9980b in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#10 0x00007fa990e9a921 in  () at /usr/lib64/evolution-ews/libcamelews-
priv.so
#11 0x00007fa9a071e203 in camel_folder_synchronize_sync ()
    at /usr/lib64/libcamel-1.2.so.62
#12 0x00007fa9a076bd20 in  () at /usr/lib64/libcamel-1.2.so.62

        Hi,
apart of missing the debuginfo for evolution-data-server and
evolution-ews, it would make more sense to file bugs like this as bugs,
because this is a mailing list for user questions and because it's much
easier to track such things in the bug tracker. I cannot tell where
exactly the problem is, but let's start here:
https://gitlab.gnome.org/GNOME/evolution-ews/issues/new

> From the little the backtrace shows, it seems to me that one of your
EWS folders has removed a message on the server and evolution-ews tries
to remove it also from the local cache. Though, it's only a guess.

As a quick workaround (if it's really about it), let evo-ews download
the folder content from scratch by moving away
  ~/.cache/evolution/mail/<ews-account-id>/folders.db
I'd not delete it, in case you'd like to reproduce the crash, thus it
could be returned back. The folder in question, if you've configured
more mail accounts, should have a 'folder-tree' file beside that
folders.db file.
        Bye,
        Milan