After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755742 - Can't connect to a server using EWS
Can't connect to a server using EWS
Status: RESOLVED DUPLICATE of bug 755075
Product: evolution-ews
Classification: Other
Component: Miscellaneous / EWS Core
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-09-28 14:57 UTC by Iain Lane
Modified: 2015-09-29 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
console output (4.97 KB, text/plain)
2015-09-28 14:57 UTC, Iain Lane 		Details

Description Iain Lane 2015-09-28 14:57:16 UTC 
Created attachment 312309 [details]
console output

I wonder if this rings any bells.

Over on Launchpad
(https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1498945) a user is reporting that they are unable to connect to their (presumably) Exchange server using EWS. There's a log with a ton of failures in it (attached), and the following trace which we obtained using G_DEBUG=fatal-criticals.

The user says that it goes away if they downgrade to glib 2.45.7 (from 2.45.8). I can't immediately spot a commit which looks like a smoking gun to me, so I wonder if you have an idea or hopefully have already seen this. :)

+ Trace 235495

  • #0 g_logv
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gmessages.c line 324
  • #1 g_logv
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gmessages.c line 1081
  • #2 g_log
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gmessages.c line 1119
  • #3 g_return_if_fail_warning
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gmessages.c line 1128
  • #4 e_ews_connection_new_full
    at e-ews-connection.c line 2137
  • #5 e_ews_connection_new
    at e-ews-connection.c line 2207
  • #6 ews_authenticate_sync
    at camel-ews-store.c line 1732
  • #7 camel_service_authenticate_sync
    at camel-service.c line 2128
  • #8 mail_ui_session_try_credentials_sync
    at e-mail-ui-session.c line 742
  • #9 e_credentials_prompter_loop_prompt_sync
    at e-credentials-prompter.c line 1751
  • #10 mail_ui_session_authenticate_sync
    at e-mail-ui-session.c line 875
  • #11 camel_session_authenticate_sync
    at camel-session.c line 1541
  • #12 ews_connect_sync
    at camel-ews-store.c line 1188
  • #13 service_shared_connect_thread
    at camel-service.c line 555
  • #14 g_task_thread_pool_thread
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./gio/gtask.c line 1283
  • #15 g_thread_pool_thread_proxy
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gthreadpool.c line 307
  • #16 g_thread_proxy
    at /build/glib2.0-4vVXvE/glib2.0-2.46.0/./glib/gthread.c line 778
  • #17 start_thread
    at pthread_create.c line 333
  • #18 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109 






Comment 1


Iain Lane





          2015-09-28 14:57:41 UTC
        



Forgot to say: all Evo comoponents are 3.16.5.






Comment 2


maogouste





          2015-09-28 15:26:04 UTC
        



I'm the user with the problem. 

I'm in wily.

I confirm using evolution-ews in order to contact two different exchange systems. With last libglib I can't connect to exchange systems.

With an older libglib I can.

maogouste






Comment 3


Milan Crha





          2015-09-29 12:46:44 UTC
        



Thanks for a bug report. As you say glib 2.45.8, it rings a bell of bug #755075.

*** This bug has been marked as a duplicate of bug 755075 ***