That interpretation is certainly what I expect caused the problem.
Before sending my post, I looked through the ~/.cache/evolution/tasks
dir and found a cache.db that held the expected text and had moved that
away. I suspect that it existed in more than one location since it
didn't remove the issu
On Thu, 2019-10-17 at 18:12 +1030, Dan Kortschak wrote:
> Is there a way to purge this task from the tasks the evolution
> believes exist but that it cannot identify on the remote store?
Hi,
it would be definitely interesting to know what caused it [1], but if
you want to just fix the thin
Hi,
I point evolution at a variety of servers, one of them unfortunately
being a EWS server that is provided by by employer. Recently I created
a task then deleted it for uninteresting reasons.
This task no longer exists on the EWS server, but still shows up in the
tasks presented by evolution. N
