GNOME Bugzilla – Bug 738547
Evolution EWS is unable to fetch email (behind a proxy)
Last modified: 2019-03-08 16:52:07 UTC
I am behind a proxy. The usual environment variables are set up right, and evolution uses system proxy settings. EWS_DEBUG=2 output: (evolution:8996): libeews-CRITICAL **: e_ews_connection_new: assertion 'uri != NULL' failed (evolution:8996): libeews-CRITICAL **: e_ews_connection_set_password: assertion 'E_IS_EWS_CONNECTION (cnc)' failed (evolution:8996): libeews-CRITICAL **: e_ews_connection_sync_folder_hierarchy_sync: assertion 'cnc != NULL' failed (evolution:8996): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (evolution:8996): GLib-CRITICAL **: g_key_file_set_string: assertion 'string != NULL' failed (evolution:8996): libeews-CRITICAL **: e_ews_connection_get_folder_sync: assertion 'cnc != NULL' failed (evolution:8996): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (evolution:8996): libeews-CRITICAL **: e_ews_connection_sync_folder_hierarchy: assertion 'cnc != NULL' failed (evolution:8996): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (evolution:8996): libeews-CRITICAL **: e_ews_oof_settings_new_sync: assertion 'E_IS_EWS_CONNECTION (connection)' failed (evolution:8996): libeews-CRITICAL **: e_ews_oof_settings_get_state: assertion 'E_IS_EWS_OOF_SETTINGS (settings)' failed (evolution:8996): camel-ews-provider-CRITICAL **: ews_refresh_info_sync: assertion 'cnc != NULL' failed (evolution:8996): camel-WARNING **: CamelEwsFolder::refresh_info_sync() reported failure without setting its GError (evolution:8996): libeews-CRITICAL **: e_ews_connection_get_items_sync: assertion 'cnc != NULL' failed (evolution:8996): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (evolution:8996): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (evolution:8996): camel-WARNING **: CamelEwsFolder::get_message_sync() reported failure without setting its GError (evolution:8996): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed And a gdb backtrace at the failure:
+ Trace 234226
On going into edit account->receiving email and hitting Fetch URL, I get a "unable to connect to host <url>" If I disable the proxy entirely in evolution's settings, "Fetch URL" succeeds, but everything else still doesn't work.
(In reply to comment #0) > (evolution:8996): libeews-CRITICAL **: e_ews_connection_new: assertion 'uri != > NULL' failed Thanks for a bug report. The above quoted runtime warning indicates a misconfiguration of the account. I suggest to remove the EWS account and configure it from scratch, make sure to click 'Fetch URL' during the initial configuration. If the runtime warning will persist, then something odd is hapenning in the bacground (do you configure your account through GNOME Online Accounts or directly in evolution?). The proxy issue itself can be in libsoup, it had an issue when using https: proxy. See bug #724316.
FWIW I believe this account is automatically provisioned by my script at http://david.woodhou.se/setup-evolution.sh which *ought* to be doing things right (and if it isn't it ought to be doing them wrong for everyone and not just Vishal). I'd already asked Vishal to click 'Fetch URL' and try again before reporting the bug. If you remove the account, please back up the files in ~/.config/evolution/sources before doing so. I'd like to track down *what* went wrong if recreating it through the GUI makes things better. We *really* need an officially supportable way to provision accounts automatically, btw :)
This account also *used* to work fine and suddenly stopped working recently, didn't it?
David, Yes this was an account that has been working fine until recently. Milan, I could try setting up the account again, but really, I'd simply be using the script David referenced above :) (And I will back up the data in .config)
Milan's request is for you to add the account manually through the GUI, not by running my script again.
Ok, I seem to be back up again after configuring the account through the GUI. I did have to turn the proxy settings to "Direct" as "Use system settings" could not connect to the internal servers while doing "Fetch URL"
Thanks. Could you send David (do *not* upload it here) current and the backup of ~/.config/evolution/sources , thus he can check the difference, please? And as you says it used to work, what did change? Do you do any update of evolution/-ews? Or libsoup was updated?
Milan, Thanks, I will follow up with David offline. I may have updated those - don't know how I can find out if/which packages were updated now. This was about a week ago..
Created attachment 288778 [details] yum update history
Yum has a convenient history feature :) Attached the updated packages closest to and before the breakage.
(In reply to Vishal Verma from comment #8) > Thanks, I will follow up with David offline. Has this happened? What was the outcome?
I'm not sure if we ever bottomed out on this particular issue. Going back through the comments, it looks like re-provisioning through the GUI had worked, but subsequently, I've provisioned other systems via the automated script, and haven't had a failure with a similar signature again. I think we can close this as can't reproduce.