Cannot sign in to Outlook with Evolution (version 3.48.3)

Hi, I cannot sign in to my private Outlook account since a few months. I’m using version 3.48.3 on Ubuntu (Flatpak).

This is the logfile when opening Evolution, I’ve already added my account. I’ve also enabled debugging via the environment variables.

This error shows up when opening:

When clicking “Reconnect” and completing the wizard finally leads to this error:

Gtk-Message: 22:57:19.813: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:19.814: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:20.082: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:20.084: Failed to load module "canberra-gtk-module"

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.221: e_ews_connection_new_full: assertion 'uri != NULL' failed

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.221: e_ews_connection_set_password: assertion 'E_IS_EWS_CONNECTION (cnc)' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.221: g_object_bind_property_full: assertion 'G_IS_OBJECT (target)' failed

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.221: e_ews_connection_sync_folder_hierarchy_sync: assertion 'cnc != NULL' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.221: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.221: invalid (NULL) pointer instance

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.221: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(evolution.bin:28): GLib-CRITICAL **: 22:57:20.221: g_key_file_set_string: assertion 'string != NULL' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.223: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(evolution.bin:28): camel-ews-provider-CRITICAL **: 22:57:20.224: ews_initial_setup_with_connection_sync: assertion 'connection != NULL' failed

(evolution.bin:28): camel-WARNING **: 22:57:20.224: CamelEwsStore::initial_setup_sync() reported failure without setting its GError

(evolution.bin:28): e-mail-engine-WARNING **: 22:57:20.224: mail_folder_cache_note_store_thread: Failed to run initial setup for 'david.kroell@outlook.com': Unknown error

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.224: e_ews_connection_sync_folder_hierarchy_sync: assertion 'cnc != NULL' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.224: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(evolution.bin:28): camel-ews-provider-WARNING **: 22:57:20.224: Unable to fetch the folder hierarchy.


(evolution.bin:28): GLib-CRITICAL **: 22:57:20.224: g_propagate_error: assertion 'src != NULL' failed

(evolution.bin:28): camel-ews-provider-CRITICAL **: 22:57:20.262: ews_initial_setup_with_connection_sync: assertion 'connection != NULL' failed

(evolution.bin:28): camel-WARNING **: 22:57:20.262: CamelEwsStore::initial_setup_sync() reported failure without setting its GError

(evolution.bin:28): e-mail-engine-WARNING **: 22:57:20.262: mail_folder_cache_note_store_thread: Failed to run initial setup for 'david.kroell@outlook.com': Unknown error

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.262: e_ews_connection_sync_folder_hierarchy_sync: assertion 'cnc != NULL' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.262: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(evolution.bin:28): camel-ews-provider-WARNING **: 22:57:20.262: Unable to fetch the folder hierarchy.


(evolution.bin:28): GLib-CRITICAL **: 22:57:20.262: g_propagate_error: assertion 'src != NULL' failed

(evolution.bin:28): evolution-ews-CRITICAL **: 22:57:20.439: e_ews_connection_sync_folder_hierarchy_sync: assertion 'cnc != NULL' failed

(evolution.bin:28): GLib-GObject-CRITICAL **: 22:57:20.439: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(evolution.bin:28): camel-ews-provider-WARNING **: 22:57:20.439: Unable to fetch the folder hierarchy.


(evolution.bin:28): GLib-CRITICAL **: 22:57:20.439: g_propagate_error: assertion 'src != NULL' failed

** (process:78235): WARNING **: 22:57:20.462: Error writing credentials to socket: Error sending message: Broken pipe
Gtk-Message: 22:57:20.532: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:20.534: Failed to load module "canberra-gtk-module"
[OAuth2] 2023-06-25 22:57:50.805 - Loading URI: 'https://login.microsoftonline.com/common/oauth2/authorize?response_mode=query&redirect_uri=https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Foauth2%2Fnativeclient&client_id=20460e5d-ce91-49af-a3a5-70b6be7486d1&login_hint=david.kroell%40outlook.com&response_type=code&resource=https%3A%2F%2Foutlook.office365.com'
Gtk-Message: 22:57:51.011: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:57:51.028: Failed to load module "canberra-gtk-module"

(evolution.bin:28): GLib-GIO-WARNING **: 22:57:52.898: Your application did not unregister from D-Bus before destruction. Consider using g_application_run().

Hi,
those runtime warnings involving “evolution-ews”, or “ews”, are not
good. By any chance, do you have configured an Exchange account both
directly in the Evolution and in the GNOME Online Accounts? I suggest
you use only the account configured in the Evolution.

The error returned from the server you see is discussed here:

See

for a bit more details.

Bye,
Milan

Hi, no, I don’t use GNOME Online Accounts, only those in Evolution.

I know this error reported in the issue already. I opened it.

Do you have any other suggestions?

Hi,
do you mean even when you enable the version 2.0 protocol and do the
things I referenced earlier (maybe run flatpak kill org.gnome.Evolution
to ensure the background processes take the change), then you still get
the error about not using version 2.0 of the protocol?

What about creating a fresh new account, where you’d select the right
settings from the very beginning?

The runtime warnings should be gone when you configure the accounts
from scratch. I do not know how those could happen. I know they
sometimes show up with the GNOME Online Accounts accounts, which is the
reason why I mentioned them. You can see the recognized accounts in
Edit->Accounts.
Bye,
Milan

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.