Attached is the log for 0.16. What I find interesting is that 0.18 is logging twice. Eg: gabbleauthentication-DEBUG: 10/21/2013 16:13:21.904870: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:836): Starting authentication gabbleauthentication-DEBUG: 10/21/2013 16:13:21.904870: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:836): Starting authentication gabbleauthentication-DEBUG: 10/21/2013 16:13:22.139523: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:548): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data gabbleauthentication-DEBUG: 10/21/2013 16:13:22.139523: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:548): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data
but 0.16 is only logging once: gabbleauthentication-DEBUG: 10/24/2013 21:24:57.750232: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:814): Starting authentication gabbleauthentication-DEBUG: 10/24/2013 21:24:58.174243: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:520): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data Don't know if this is related or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1223436 Title: telepathy-gabble 0.18 does not work with jabberd2 Status in “telepathy-gabble” package in Ubuntu: New Status in “telepathy-gabble” source package in Saucy: New Bug description: If I upgrade to telepathy-gabble 0.18.0-1 or 0.18.1-1, I can no longer connect to a jabberd2 server. The jabberd2 c2s.log simply has: Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] connect Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] disconnect jid=unbound, packets: 0 If I downgrade to 0.16.6-1ubuntu1, it starts working again: Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] connect Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] disconnect jid=unbound, packets: 0 Tue Sep 10 11:14:01 2013 [notice] [12] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=xxx, TLS negotiated Tue Sep 10 11:14:01 2013 [notice] [12] bound: jid=xxx/xxx I can see this by trying to connect with empathy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1223436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
