On Wed, 2017-07-19 at 10:33 +0200, Milan Crha wrote: > On Tue, 2017-07-18 at 23:36 +0200, Rudolf Künzli wrote: > > I can't repeat the problem easily... > > Hi, > okay, that's a pita. Could you keep running evolution-addressbook- > factory with EWS debugging on in the background, and when it'll > strike > back, then check the log for the backendError message and what > preceded > it, please? That would show what evolution-ews passed to the server > and > eventually shed a bit of light on the issues. > > To do that: > a) close evolution > b) open terminal and run in it: > $ EWS_DEBUG=2 /usr/libexec/evolution-addressbook-factory -w > &>log.txt > Actual path can differ on your system. > c) run evolution and use it as before > > The log contains all the communication between the server and the > client, exposing all the private information down to your contacts, > but > the only interesting part is the one with the backendError and what > precedes it. Maybe file a bug report in GNOME bugzilla and we can > follow there. Feel free to send the relevant part of the log only to > me, but reference that bug report, otherwise I'd overlook it in my > spam > folder. Definitely keep the log for later use, in case I'd need more > information from it. Also note that the file as such will be fully > populated only after the factory is properly closed, due to caching, > which it might to roughly 10 seconds after you close evolution (and > all > other clients connected to it, if any). > Bye, > Milan > Hi Milan,
I did as you described above. I had no error the whole day up to now. The log file is empty. Thanks > _______________________________________________ > evolution-list mailing list > evolution-list@gnome.org > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
