On Wed, 2017-09-20 at 11:02 +0200, Herr Oswald wrote:
> I still vote for an attempt to make evo more robust against
> network losses and other incidents and provide an enhanced reconnect
> feature
Hi,
I agree. As Pete mentioned, Evolution doesn't talk to NetworkManager
directly, it uses, and relies on, a GNetworkMonitor object provided by
glib, which has multiple implementations how to check for existing
connection. I do not say it's GNetworkMonitor fault here, I only know
that some network setups are not properly handled by it. The issue can
be completely elsewhere, like some connection attempt being stuck with
old route or something like that, though most of the connections in
Evolution (and also evolution-data-server) have set connection timeout
to 90 seconds.
You mentioned in the launchpad bug report this error message:
> "Failed to lookup credentials: Failed to get password from
> GOA: timeout"
It means that it's not on the evolution side, but on the GOA
(goa-daemon) side, that it does something such long that the request
made by evolution-data-server times out. Accidentally, I made some
changes in eds recently [1], which ignore this error when calling
certain function of the GOA interface. The main changes should go to
GOA, though.
Bye,
Milan
[1] the change landed for evolution-data-server 3.27.1+ and 3.26.1+:
https://git.gnome.org/browse/evolution-data-server/commit/?id=040788e758ddf75bbb9a9
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
