On reconnects, xchat's net-monitor plugin doesn't reuse SSL, the port number or server password

Thank you for your bug. I don't confirm that, works fine on my feisty desktop. How do you try to reconnect? With the menu item?

Yes, I can definitely reproduce it. I disconnected from the network by enabling/disabling my wireless in NetworkManager. xchat apparently saw this (I presume on dbus) and greyed out all my connections. When I reconnected NetworkManager it correctly got on to freenode, but it says

 Looking up irc.canonical.com..
 Connecting to irc.canonical.com (82.211.81.183) port 6667..
 Stopped previous connection attempt (pid=8163)
 Looking up irc.canonical.com..
 Stopped previous connection attempt (pid=8374)
 Looking up irc.canonical.com..
 Connecting to irc.canonical.com (82.211.81.183) port 6667..

which is the wrong number. I just confirmed that my configurationi is correct. Right-clicking Connect on the server does not help, but typing "/server -ssl ...." does work, as does closing the tab and choosiing IRC/Connect.

Do you get the same behaviour when using the menu item to reconnect? Did you configure a new server for canonical? There was http://bugzilla.gnome.org/show_bug.cgi?id=346279 similar upstream which has been closed. Reconnecting works fine on my desktop

Using the context menu of the server to reconnect seems to work ok.

I don't know what you mean by "a new server". The server is not in the default xchat settings, so I added a new server and then added one server to it, configuring ssl and the port as per the wiki page.

~/.xchat2/servlist_.conf has

v=0.16

N=Canonical
I=poolie
R=Martin Pool
P=*********
J=#canonical
E=UTF-8 (Unicode)
F=46
D=0
S=irc.canonical.com/****

the first asterisks is the password and the second is the decimal port number.

I've forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=424852

This bug just cost me 2 weeks without IRC... please fix it, and add an option to change the port one wishes to connect to.

On 8/11/07, David Corrales <email address hidden> wrote:
> This bug just cost me 2 weeks without IRC... please fix it, and add an
> option to change the port one wishes to connect to.

There already is an option to set the port per server. Do you want
something else?

fwiw I have not seen the reconnection bug with gutsy's xchat (rather
than xchat-gnome), but I have not specifically tested it either.

--
Martin

I'm seeing this issue frequently under 0.18 here, with somewhat more dire implications. I've got xchat-gnome configured to connect via ssl to a proxy with a password. When this auto-reconnect bug pops up, it'll switch ports, or sometimes even the hostname, and disable ssl. As a consequence, sensitive authentication information is suddenly being sent via cleartext to a remote server without my prompting. To me this makes it a pretty serious security issue.

Sounds like it may be the same issue as https://bugs.launchpad.net/xchat-gnome/+bug/133894 (and indirectly http://bugzilla.gnome.org/show_bug.cgi?id=480195)

Marking Ubuntu task as "Won't Fix" based on upstream's response that there isn't time to implement this. If someone is able, I suggest working with upstream and getting the bug fix there, after which Ubuntu will get the fix via our normal development process. Thanks!

It's still affecting precise, and quite a big pain in the.

It seems like this only happens if the network-manager plugin is enabled.

This still happens for me on Quantal, beta 2 with xchat-gnome 0.3.0. It only happens with servers that are configured to use SSL. Ones like freenode reconnect just fine. I usually run into this when my laptop wakes from sleep.