It seems like this only happens if the network-manager plugin is
enabled.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/97253
Title:
xchat reconnects on the wrong port number
To manage notificati
It's still affecting precise, and quite a big pain in the.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/97253
Title:
xchat reconnects on the wrong port number
To manage notifications about this
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!
** Changed in: xchat-gnome (Ub
** Changed in: xchat-gnome
Importance: Unknown => Medium
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@l
** Changed in: xchat-gnome
Status: New => Confirmed
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@li
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)
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a mem
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, sensiti
** Changed in: xchat-gnome (Ubuntu)
Status: Confirmed => Triaged
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
de
On 8/11/07, David Corrales <[EMAIL PROTECTED]> 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 reconne
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.
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
** Changed in: xchat-gnome (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs
--
xchat reconnects on the wrong port number
https://bugs.launchpad.net/bugs/97253
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Changed in: xchat-gnome (upstream)
Status: Unknown => Unconfirmed
--
xchat reconnects on the wrong port number
https://launchpad.net/bugs/97253
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I've forwarded that upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=424852
** Changed in: xchat-gnome (Ubuntu)
Status: Unconfirmed => Confirmed
** Bug watch added: GNOME Bug Tracker #424852
http://bugzilla.gnome.org/show_bug.cgi?id=424852
** Also affects: xchat-gnome (upstream) via
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
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
--
xchat reconnects on the wrong port number
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 ir
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?
** Changed in: xchat-gnome (Ubuntu)
Importance: Undecided => Low
--
xchat reconnects on the wrong port number
https://launchpad.net/bugs/97253
--
desktop-bugs mail
17 matches
Mail list logo
