On Tue, 2018-09-25 at 17:26 +0200, Torsten Krah via evolution-list
wrote:
> I got this windows 2 times already just today ... :-| - anything I
> can look for in the logs why it fails to refresh the token?
Hi,
it depends which part issued it. I'm not sure if it can be seen from
the GUI. Thus I'd probably open 4 terminals and run all the processes
there in the below order. Export these environment variables in each of
these terminals first:
$ export CAMEL_DEBUG=imapx:io
$ export CALDAV_DEBUG=all
$ export WEBDAV_DEBUG=all
$ export G_MESSAGES_DEBUG=all
$ export LIBGDATA_DEBUG=255
then in the first terminal:
$ ESR_DEBUG=1 /usr/libexec/evolution-source-registry
wait a bit and in the second terminal:
$ /usr/libexec/evolution-addressbook-factory -w
wait a bit and in the third terminal:
$ /usr/libexec/evolution-calendar-factory -w
wait a bit and in the fourth terminal:
$ evolution
Then just use it and wait until the re-grant dialog shows up. Each of
the console can contain some information, maybe "401 Unauthorized"
responses on the factory and registry processes, maybe something else
on the evolution console (which covers the mail part).
I'm not sure what exactly to look for, but the failures sometimes also
include explanation, which might not always get into the UI, though it
can help.
Actual path to the processes can differ in your distribution.
Hope it helps,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
