Re: [Evolution] troublesome cache

[Ralf Mardorf <silver bullet zoho com>]

On Fri, 05 Feb 2021 16:40:13 +0000, Pete Biggs wrote:
> Before playing with any of the configuration files you must ensure that
> Evolution, and all it's ancillary programs are shut down.  Some of them
> (such as dconf) maintain in-memory copies of the data that are written
> out when the program shuts down.  (This DOES NOT apply to the cache.)

Btw. dconf is probably a tmpfs in /run/user/*/dconf/user , IOW not only
in ~/.config/dconf/user, but it's unlikely related to the "issue".

If the OP should insist in his kind of getting rid of the issue, a
workaround could be to purge the evolution and evolution-data-server
related packages...

    evolution
    evolution-common
    evolution-dev
    evolution-plugin-bogofilter
    evolution-plugin-pstimport
    evolution-plugin-spamassassin
    evolution-plugins
    evolution-plugins-experimental
    libevolution

https://tracker.debian.org/pkg/evolution

    evolution-data-server (21 bugs: 0, 18, 3, 0)
    evolution-data-server-common
    evolution-data-server-dev
    evolution-data-server-doc
    evolution-data-server-tests
    gir1.2-camel-1.2
    gir1.2-ebackend-1.2
    gir1.2-ebook-1.2
    gir1.2-ebookcontacts-1.2
    gir1.2-ecal-2.0
    gir1.2-edatabook-1.2
    gir1.2-edatacal-2.0
    gir1.2-edataserver-1.2
    gir1.2-edataserverui-1.2
    libcamel-1.2-62
    libcamel1.2-dev
    libebackend-1.2-10
    libebackend1.2-dev
    libebook-1.2-20
    libebook-contacts-1.2-3
    libebook-contacts1.2-dev
    libebook1.2-dev
    libecal-2.0-1
    libecal2.0-dev
    libedata-book-1.2-26
    libedata-book1.2-dev
    libedata-cal-2.0-1
    libedata-cal2.0-dev
    libedataserver-1.2-25
    libedataserver1.2-dev
    libedataserverui-1.2-2
    libedataserverui1.2-dev

https://tracker.debian.org/pkg/evolution-data-server

...then to boot a live DVD of e.g. Ubuntu, to mount the Ubuntu install
and to delete all the mentioned evolution related paths, excepted of
dconf paths, that anyway aren't related to the "issue".

After that to boot the install again, to install Evolution again.
Something similar was already pointed out ;), but maybe it's easier to
understand that way ;).

FWIW there are commands such as "ps" and "lsof" available, that could
be used to see possible pitfalls without a reboot at all.