Gabble gives up when restarted, trying to connect through proxy

[mikus]

This is a follow-on to #6542. Changed jabber with 'sugar-control-panel', then restarted Sugar (ctl-alt-erase). Did not get a connection to the specified jabber server.

G1G1, Joyride 1852+, no wireless -- *wired* connection through an USB-ethernet adapter, then through a proxy system to the internet. What happened was that when Sugar was restarted, the IPv4 connection to the local LAN was now made through 'eth1', not 'eth0'.

Looking at telepathy-gabble.log, where with Loudmouth 1.2.3 gabble executed an 'assert' when the specified jabber server was online, now with Loudmouth 1.3.4 gabble appears to give up executing (whether or not the specified jabber server is online). [The current log entries correspond with those of # 6542, and end just before the 'assert' entry shows up in the # 6542 log.]

[mikus]

olpc-netlog after restarting Sugar

[gdesmott]

According to your log, Gabble was properly connecting. Please be more patient and provide another log.

[mikus]

another log - looks the same to me

[mikus]

Found the basic cause of not being able to connect to the jabber server -- my proxy was rejecting the XO's "CONNECT packet". Reinstalled the proxy, and can now connect to the Jabber server. When Gabble was thwarted, ought it to have simply "evaporated" as it did ?

[Apparently the reassignment of the wired connection from 'eth0' to 'eth1' did not affect my XO's communication capability.]

[mikus]

snapshot of "CONNECT" packet being rejected

[mikus]

connected to jabber server, but eventually my Neighborhood depopulated

[gdesmott]

Closing this bug then. Let's discuss the "Gabble doesn't try to reconnect problem" on #6889

[gregorio]

Milestone Never Assigned deleted