Bug 49599

Summary: Wocky refuses to connect to WLM server
Product: Wocky Reporter: Olivier Crête <olivier.crete>
Component: GeneralAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED NOTOURBUG QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: major    
Priority: medium CC: xclaesse
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Gabble log

Description Olivier Crête 2012-05-07 11:36:43 UTC
Created attachment 61168 [details]
Gabble log

I think the problem is that wocky sends a <iq type='set'><session>.. and expects the next stanza to be the matching <iq type='result'>. But the WLM server sends a <presence>.. I don't see why that would be invalid.. This is all done inside wocky-connector.c .. I guess the thing needs to be modified to expect random stanzas...

This is kind of major as it blocks connecting to WLM which is one of our major features for GNOME 3.4
Comment 1 Xavier Claessens 2012-05-07 12:21:41 UTC
According to Sjoerd that's not valid XMPP, so I reported:
http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/cf5721a8-fd4f-4bc2-8f8f-78edd4caec64

Note that it works for most people, you are the 3rd to report that issue though.
Comment 2 Olivier Crête 2012-05-07 13:01:10 UTC
I was connected to MSN using the MSN protocol from other places, if I disconnect, then it works. I guess the server was forwarding me the presence of the other resources.
Comment 3 Guillaume Desmottes 2012-05-07 23:11:56 UTC
Also reported on https://bugzilla.gnome.org/show_bug.cgi?id=675273
Comment 4 Will Thompson 2012-11-06 16:34:33 UTC
Olivier, do you still get this? Microsoft say at the end of http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/cf5721a8-fd4f-4bc2-8f8f-78edd4caec64 that they fixed it in August.
Comment 5 Olivier Crête 2012-11-06 16:57:39 UTC
It seems to connect now!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.