(gutsy) cannot reconnect to OFTC

Thank you for taking the time to report this bug and helping to make Ubuntu better. I cannot reproduce this bug, if there's only one how they can try to connect to the other server? it make no sense. Is this a fresh installation of Gutsy? may you try to reproduce this report with another user? thanks in advance.

This is an upgraded gutsy.

Note that the problem happens only if I *get* disconnected, not if I manually disconnect (i.e. right-clicking on the network and choosing "disconnect" does not cause the problem.) The way I am disconnected is generally by the wireless network dropping; it should be reproducible by disabling and re-enabling wireless, or by ifdown on a standard ethernet connection, or possibly by physically unplugging a wired ethernet connection.

To answer your question "if there's only one how they can try to connect to the other server", I don't know. It seems like it takes the server's host name ("Your host is xenon.oftc.net") and tries to reconnect to that.

That's what i tried and i cannot reproduce it, did you tried it with another new user?

Closing this bug since no more information has been provided, feel free to re open it if you still get the issue. thanks in advance.

I still have this problem. I have trouble getting x-chat to actually disconnect; if I ifdown it actually just lags forever (or at least a long time) until I reconnect. Once I do, the messages flow again, without disconnecting me from IRC. It might be that I simply need to wait longer; however, when the disconnect is unintentional, the disconnect happens immediately.

If you have the ability, it might be possible to duplicate by either powering of an access point, or simply roaming out of range of it.

Do you have dns configuration issues? Using different server names should work correctly

No, no DNS configuration issues. The server's idea of its host name simply doesnt resolve. See http://www.zoneedit.com/lookup.html?host=xenon.oftc.net&type=A&server=&forward=Look+it+up for an example. The question is, why is xchat-gnome attempting to connect to a server name which is not in the network's list of servers?

Looking at the code, on line 780 of src/common/server.c it looks like it attempts to reconnect to serv->hostname. I debugged xchat-gnome, and found that, indeed, serv->hostname is set to the server's alias at reconnect time rather than being a resolvable host. At first I thought this was being set on line 1662 of the same file, but apparently not. After further examination, I think it's actually line 2872 of src/common/outbound.c Not sure though, it could be either place, or somewhere else entirely. There aren't a whole lot of places where serv->hostname is set though ( I think those are the only two)

I've sent the bug and your comments upstream on http://bugzilla.gnome.org/show_bug.cgi?id=480195

Same issue as https://bugs.launchpad.net/xchat-gnome/+bug/97253 (and indirectly http://bugzilla.gnome.org/show_bug.cgi?id=424852?