Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#6885 closed defect (invalid)

Gabble gives up when restarted, trying to connect through proxy

Reported by: mikus Owned by: Collabora
Priority: low Milestone:
Component: telepathy-gabble Version: Development build as of this date
Keywords: Cc: mikus@…
Blocked By: Blocking:
Deployments affected: Action Needed:
Verified: no

Description

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.]

Attachments (4)

logs.CSN74804910.2008-04-12.11-58-04.tar.bz2 (27.9 KB) - added by mikus 7 years ago.
olpc-netlog after restarting Sugar
logs.CSN74804910.2008-04-15.16-55-48.tar.bz2 (27.8 KB) - added by mikus 7 years ago.
another log - looks the same to me
lan.packets (12.9 KB) - added by mikus 7 years ago.
snapshot of "CONNECT" packet being rejected
logs.CSN74804910.2008-04-15.20-15-38.tar.bz2 (732.6 KB) - added by mikus 7 years ago.
connected to jabber server, but eventually my Neighborhood depopulated

Download all attachments as: .zip

Change History (9)

Changed 7 years ago by mikus

olpc-netlog after restarting Sugar

comment:1 Changed 7 years ago by gdesmott

  • Component changed from distro to telepathy-gabble
  • Owner changed from jg to Collabora

comment:2 Changed 7 years ago by gdesmott

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

Changed 7 years ago by mikus

another log - looks the same to me

comment:3 Changed 7 years ago by mikus

  • Priority changed from normal to low

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.]

Changed 7 years ago by mikus

snapshot of "CONNECT" packet being rejected

Changed 7 years ago by mikus

connected to jabber server, but eventually my Neighborhood depopulated

comment:4 Changed 7 years ago by gdesmott

  • Resolution set to invalid
  • Status changed from new to closed

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

comment:5 Changed 6 years ago by gregorio

  • Milestone Never Assigned deleted

Milestone Never Assigned deleted

Note: See TracTickets for help on using tickets.