Other laptops aren't displayed in Neighborhood View

[wad]

Connecting to a school server, using an WiFi access point, there are times when a laptop associates properly with the school AP, and even connects with the school presence service (i.e. it start running gabble), yet it doesn't show any other laptops in its neighborhood view.

Running build 703 on the laptop, and build 160 on the school server.

Logs, packet traces, and more information about the test setup can be found at: http://wiki.laptop.org/go/Collab_Network_School_Wifi_Tests#Test_0410A

[gdesmott]

Humm that's interesting.

From http://xs-dev.laptop.org/mesh/test0410/t0410A/X68/sugar/presenceservice.log :

1207875746.800724 WARNING s-p-s.buddy: /org/freedesktop/Telepathy/Connection/gabble/jabber/_3747e2b38d61d38cf21eabbac23b3e1958f76a264_40schoolserver_2eannex_2exs_2elaptop_2eorg_2fTelepathy does not support BuddyInfo - unable to set my own buddy properties
1207875746.805054 WARNING s-p-s.buddy: /org/freedesktop/Telepathy/Connection/gabble/jabber/_3747e2b38d61d38cf21eabbac23b3e1958f76a264_40schoolserver_2eannex_2exs_2elaptop_2eorg_2fTelepathy does not support BuddyInfo - unable to set activities
1207875746.807752 DEBUG s-p-s.buddy: Setting current activity to '' (handle 0)
1207875746.811181 WARNING s-p-s.buddy: /org/freedesktop/Telepathy/Connection/gabble/jabber/_3747e2b38d61d38cf21eabbac23b3e1958f76a264_40schoolserver_2eannex_2exs_2elaptop_2eorg_2fTelepathy does not support BuddyInfo - unable to set current activity
1207875746.813557 WARNING s-p-s.presenceservice: Connection /org/freedesktop/Telepathy/Connection/gabble/jabber/_3747e2b38d61d38cf21eabbac23b3e1958f76a264_40schoolserver_2eannex_2exs_2elaptop_2eorg_2fTelepathy does not support OLPC activity properties
1207875746.816434 WARNING s-p-s.presenceservice: Connection /org/freedesktop/Telepathy/Connection/gabble/jabber/_3747e2b38d61d38cf21eabbac23b3e1958f76a264_40schoolserver_2eannex_2exs_2elaptop_2eorg_2fTelepathy does not support OLPC buddy info

[gdesmott]

The disco reply is received too late and its time out is fired.

** (telepathy-gabble:1656): DEBUG: connection_disco_cb: got disco error, setting no features: Request for info on schoolserver.annex.xs.laptop.org timed out

Then when we finally receive the reply but we ignore it and so we don't set the PEP feature.

** (telepathy-gabble:1656): DEBUG: connection_iq_unknown_cb: got unknown iq:

I'm wondering if it's really sane to completely ignore these replies as we know they can timeout? Or maybe we should just increase the length of the timeout?

[gdesmott]

According to Rob, we should stay "connecting" until we got the disco reply or go disconnected if it takes too long. We could increase the length of the timeout but it would be good to know why it takes so long to reply: configuration problem, congested network, server bug, ...

[gdesmott]

Proposed fix in http://monkey.collabora.co.uk/telepathy-gabble-cassidy

[gdesmott]

My fix was merged upstream and so will be included in the next release. I'll close this bug when it will reach Joyride.

[gdesmott]

Fix in Joyride since 1894.

[gregorio]

Milestone Never Assigned deleted