GNOME Bugzilla – Bug 355260
xchat-gnome is inaccessible
Last modified: 2019-02-23 02:51:38 UTC
Steps to reproduce: 0) Start x-g 1) At-poke x-g 2) Drill down to x-g's conversation view in at-poke Results: Conversation view does not expose its text to at-poke.
This is still a problem with xchat-gnome 0.18 in Ubuntu Gutsy. I suspect that if anybody wants accessible IRC chat, then they should just use pidgin which is not only accessible, but has had a special Orca script created to add several features for blind users.
Using operating system Fedora 16 Beta (mostly(fc16 (32bit) packages), xchat-gnome 0.26.1 (32bit) locates my host name but keeps displaying this: Connecting to chat.freenode.net (94.125.182.252) port 7070.. * Subject: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware * Issuer: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware * Subject: /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA * Issuer: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware * Subject: /OU=Domain Control Validated/OU=Gandi Standard Wildcard SSL/CN=*.freenode.net * Issuer: /C=FR/O=GANDI SAS/CN=Gandi Standard SSL CA * Certification info: Subject: OU=Domain Control Validated OU=Gandi Standard Wildcard SSL CN=*.freenode.net Issuer: C=FR O=GANDI SAS CN=Gandi Standard SSL CA Public key algorithm: rsaEncryption (2048 bits) Sign algorithm sha1WithRSAEncryption Valid since Jan 14 00:00:00 2011 GMT to Jan 14 23:59:59 2012 GMT * Cipher info: Version: TLSv1/SSLv3, cipher DHE-RSA-AES256-SHA (256 bits) Connected. Now logging in.. *** Looking up your hostname... *** Checking Ident *** Found your hostname *** No Ident response PASS :Not enough parameters *** Notice -- You need to identify via SASL to use this server Closing Link: 66-87-2-207.pools.spcsdns.net (SASL access only) Disconnected (Remote host closed socket). Cycling to next server in FreeNode... Disconnected (). Looking up #fedora.. Unknown host. Maybe you misspelled it? Cycling to next server in FreeNode... Disconnected (). Looking up #fedora-social.. Unknown host. Maybe you misspelled it? Cycling to next server in FreeNode... Disconnected (). Looking up #xchat-gnome on irc.freenode.net .. Unknown host. Maybe you misspelled it? Cycling to next server in FreeNode... Disconnected (). I know that address 192.168.1.1 use to be a open unsecure default address but as of now that is my address from VirginMobile MiFi2200 26C Secure up to 5 machines, 192.168.1.2, 192.168.1.3, 192.168.1.4, 192.168.1.5. Now the open unsecure default address is 192.168.0.1, 192.168.0.2, etc. If SASL it ask for is my address? >I'm assuming my Network Manager(32bit)to send it or xchat-gnome0.26.1fc16(32bit) can't pick-up on it?
xchat-gnome is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/xchat-gnome/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather reactivate the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again. You may want to switch to Hexchat (or another IRC client that suits you).