Red Hat Bugzilla – Bug 675945
xchat never connects to freenode but web freenode works fine (with vid)
Last modified: 2013-04-02 00:25:20 EDT
Description of problem:
xchat won't connect to freenode though freenode is live and well
Version-Release number of selected component (if applicable):
all the time
Steps to Reproduce:
1.go to xchat
Python interface loaded
Perl interface loaded
* Looking up irc.freenode.net.... for ever
should log in quick like a bunny
same issue here, prior to updates in the last week I was able to connect without issue, but since that time it seems to be inserting rubbish characters into the username when submitting to freenode (e.g. ~) constantly looping on the following for me with each different server:
* Looking up irc.freenode.net
* Connecting to chat.freenode.net (18.104.22.168) port 8002...
* Connected. Now logging in...
* *** Looking up your hostname...
* *** Checking Ident
* *** Found your hostname
* *** No Ident response
* *** Your username is invalid. Please make sure that your username contains only alphanumeric characters.
* Closing Link: <my ip address> (Invalid username [~_xxx]) [where xxx is my username]
* Disconnected (Remote host closed socket).
Cycling to next server in FreeNode...
* Disconnected ().
funnily enough, I can connect via konversation, and then re-connect xchat and it works (except it detects my username in use). I have tried removing my personal preferences and recreating the connection to no avail...
oh yeah...running f16 3.3.1-3 kernel as well and xchat 2.8.8
ignore my report, issue was resolved by only using nickname for my username and putting random data into "real name" and "username" see bug 812088
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: