On Mon, 2022-01-10 at 10:45 -0500, Bridger Dyson-Smith via evolution-
list wrote:
> CAMEL_DEBUG=all
Hi,
using CAMEL_DEBUG=all is a very bad idea. There's nobody to read what
it can generate. Try to avoid that and use only targeted debugging, in
your case the EWS debugging.
> I've also tried launching from the command line; e.g. `) EWS_DEBUG=2
> CAMEL_DEBUG=all evolution >& evolution-debugging-2022-01-10.txt`, but
> without any significant change in the output.
The bracket looks odd, maybe it's just a copy&paste thing.
Try this (it should print the data into the terminal):
$ EWS_DEBUG=2 evolution
or you can try (also in your script):
$ export EWS_DEBUG=2
$ evolution
To be hundred percent sure any background evolution is not running
before you start it from a terminal do:
$ evolution --quit
first, and then verify it's not running by:
$ ps ax | grep evolution
It can print several evolution-data-server processes, which is fine.
You are looking for the `evolution` process itself.
> I'm using the following packages:
> evolution-3.42.1
> evolution-data-server-3.42.1
> evolution-ews-3.42.1
I guess there's no Flatpak involved, but checking anyway, just in case.
Bye,
Milan
_______________________________________________
evolution-list mailing list
[email protected]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
