Closed Bug 279067 Opened 21 years ago Closed 20 years ago

Unable to leave channels in Irc.Americasarmy.com

Categories

(Other Applications Graveyard :: ChatZilla, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: rtmthepenguin, Assigned: rginda)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I have tried to /leave in other Irc. address (sutch as IRC.mozilla) and it works fine, however when i try that command or /part, it will not leave hte channel but closes the tab until another person in channel speeks. a problem with the scripting of the IRC server perhaps? Reproducible: Always Steps to Reproduce: 1.Connect to irc.americasarmy.com 2.join a channel then /leave the channel 3./whois yourself to see if your still connected to the channel Actual Results: am still in the channels until i disconnect from irc.americasarmy.com Expected Results: left the channel
Works fine for me using latest ChatZilla (0.9.67).
(In reply to comment #1) > Works fine for me using latest ChatZilla (0.9.67). in that server? it seems to be the olny one. may be a problem with my firefox install. what os are you running?
Yes, that server. OS is irrelevant, but here is my UA and CZ identifcation strings: UA: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050120 CZ: Chatzilla 0.9.67 [Mozilla rv:1.8b/20050120] client.hostPlatform: MozillaWindows
(In reply to comment #3) > Yes, that server. > > OS is irrelevant, but here is my UA and CZ identifcation strings: > UA: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050120 > CZ: Chatzilla 0.9.67 [Mozilla rv:1.8b/20050120] > client.hostPlatform: MozillaWindows i worked with one of the IRC helpers in the server, he said it has somting to do with unreal ircd servers and chatzilla (im using 9.67) with nicks with bracket caratcers ex: { [ } ] join a Unreal ircd server with a nick with bracket caras and try to /part from a server.
It still works perfectly for me using the nickname "[SilverFox]".
(In reply to comment #5) > It still works perfectly for me using the nickname "[SilverFox]". is that the name you had when you signed on to the server?
(In reply to comment #6) > (In reply to comment #5) > > It still works perfectly for me using the nickname "[SilverFox]". > > is that the name you had when you signed on to the server? Edit: forgot to mention at the begining that im using the Firefox Adon of chatzilla not the one that is bundled with mozilla
(In reply to comment #6) > (In reply to comment #5) > > It still works perfectly for me using the nickname "[SilverFox]". > > is that the name you had when you signed on to the server? Yes. (In reply to comment #7) > Edit: forgot to mention at the begining that im using the Firefox Adon of > chatzilla not the one that is bundled with mozilla They are one and the same. :)
Reporter, can you still reproduce this bug on the latest version of ChatZilla? Another bug concerning a similar problem was recently fixed, I'm fairly certain you should no longer have this problem in the latest version (0.9.68.5)
(In reply to comment #9) > Reporter, can you still reproduce this bug on the latest version of ChatZilla? > Another bug concerning a similar problem was recently fixed, I'm fairly certain > you should no longer have this problem in the latest version (0.9.68.5) Yes im still experencing the same problem with the current version, have also Wrote 0's to the HD since then. as of right now i have found a workaround suitiable for me; I have simply aliased my nick to a name that no longer includes [ and ]. I would still like to see it fixed however.
OS: Windows 2000 → All
Hardware: PC → All
I can't see this problem either with CVS chatzilla. Feel free to reopen if you can reproduce this again.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.