Bug 45915

This does not use telepathy-butterfly, but telepathy-gabble. Could you please attach gabble logs?

Created attachment 60307 [details]
gabble failing connection to Windows Live

attaching log;

according to IRC: is _not_ be related to "see-other-host" implementation ( http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/5a0ca19f-46d5-4c23-9921-8b032d562c2e )

I was able to connect today just _once_ to Windows Live using XMPP.

I can't connect again even after redoing the steps.

Even so, here are the steps I've done:
Go to https://profile.live.com/home/Services/?view=manage , delete all "Gnome".
Go to "Passwords and Keys", check if anything remotely like an "Online Account" entry gone bad is there (I had two for "Windows Live" there even though I had only one "Windows Live" account)
Go to "Online Accounts", delete all "Windows Live".
Re-add "Windows Live".
Try to connect. It may work.


EDIT after writing: I was able to connect two additional times. Unfortunately, I couldn't get a good log for comparison and subsequent attempts failed.

I got a log for a successful connect!

Is it possible that a gabble plugin/thread is spawned twice hence reading the buffer in an out of order fashion?

On the SUCCESS log, only one init of gabble is found.
On the FAIL log, two inits are found.

I'll attach snippets of them.

Created attachment 60479 [details]
failed connect

Created attachment 60480 [details]
success connect

Created attachment 61449 [details]
Failed connection attempt

I think I'm affected by the same bug.
I've used Gnome Online Accounts to connect to my Windows Live account yesterday.

I've was online yesterday but today when my laptop woke from suspend I just keep getting "Network error".

I've tried closing empathy and killing all processes containing the name telepathy and mission-control. The connection still fails.

I've attached a log file.
I cleared the log
Hit reconnect
When I got the error again I pressed pause and saved the log to a file.

Let me know if you want me to try stuff out.

Still not working, despite http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/cf5721a8-fd4f-4bc2-8f8f-78edd4caec64 saying something was fixed (at the bottom).

I now have another issue that prevent me to connect, it is bug #51033. Please check your gabble logs if you have "see-other-host" there.

Yes, now I have:

_end_element_ns: Received stanza
* error xmlns='http://etherx.jabber.org/streams'
    * see-other-host xmlns='urn:ietf:params:xml:ns:xmpp-streams'
        "BAYMSG1020321.gateway.edge.messenger.live.com"

connector_error_disconnect (connection.c:1772): connection failed: WOCKY_XMPP_STREAM_ERROR_SEE_OTHER_HOST (#17): 

I'll subscribe bug #51033 and ignore this one for now (since "see-other-host" didn't appear before).

If after bug #51033 is fixed I still can't connect I'll repost here.

Let's close this bug, MS dev claims they fixed it and in any case it's not gabble's fault but server's.

Nowadays the issue is the lack of support for see-other-host, which is our fault and tracked in bug #51033

Sorry, now that see-other-host is fixed, I get this error again.

I was able to connect once and afterwards it failed subsequent attempts.

connector_error_disconnect (connection.c:1772): connection failed: WOCKY_CONNECTOR_ERROR_SESSION_FAILED (#14): Session iq response invalid
connector_error_disconnect (connection.c:1772): connection failed: WOCKY_CONNECTOR_ERROR_SESSION_FAILED (#14): Session iq response invalid

(as usual, duplicated entries)

(In reply to comment #12)
> Sorry, now that see-other-host is fixed, I get this error again.
> 
> I was able to connect once and afterwards it failed subsequent attempts.
> 
> connector_error_disconnect (connection.c:1772): connection failed:
> WOCKY_CONNECTOR_ERROR_SESSION_FAILED (#14): Session iq response invalid
> connector_error_disconnect (connection.c:1772): connection failed:
> WOCKY_CONNECTOR_ERROR_SESSION_FAILED (#14): Session iq response invalid
> 
> (as usual, duplicated entries)

That issue is not related. It is server's fault and Microsoft is working on fixing it. See http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/cf5721a8-fd4f-4bc2-8f8f-78edd4caec64

Retry to connect, and after a few attempts it usually works. I've also noticed that not connecting the same account from other places helps.

Actually resolution is NOTOUTBUG, not FIXED. There is nothing we can do about this.

Ah ok sorry. I reopened it because I thought it was already fixed server side. I had failed to see your later replies since June 19 on that link.

Sorry for the noise and thanks for the clarification :)