[Evolution-hackers] evolution-ews connection problem
This is a bit weird: I have two FC14 systems both connecting identically (the evolution configuration is actually cloned between them). One connects just fine, but the other won't do the initial mailbox scan. The log is full of (evolution:2589): libsoup-CRITICAL **: soup_session_get_connection: assertion `soup_connection_get_state (item-conn) != SOUP_CONNECTION_DISCONNECTED' failed If I click on an individual mailbox, then it will refresh it, but it doesn't happen automatically. James ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution-ews connection problem
On Tue, 2011-07-05 at 17:47 +0300, James Bottomley wrote: Well, as I said, they're both FC14 systems, so yes, the version on both is libsoup-2.32.2-1.fc14.i686 James Try to run EWS_DEBUG=2 evolution the send the log file ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers - Intel Electronics Ltd. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution-ews connection problem
On Tue, 2011-07-05 at 18:01 +0300, Ocheretny, Pavel wrote: On Tue, 2011-07-05 at 17:47 +0300, James Bottomley wrote: Well, as I said, they're both FC14 systems, so yes, the version on both is libsoup-2.32.2-1.fc14.i686 James Try to run EWS_DEBUG=2 evolution the send the log file Would you believe it wouldn't reproduce with EWS_DEBUG=2? Further, whatever it was is now fixed and it won't reproduce on the system with or without EWS_DEBUG set. I suspect it was some state file somewhere, since evolution wouldn't shut down cleanly either. James ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
