Open Bug 932766 Opened 6 years ago Updated 6 years ago
When trying to /quit, "Error: Not connected" should be disregarded
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131023 Firefox/17.0 ID:20131023000506 CSet: c3750e0515f7 ChatZilla 0.9.90.1 Reproducible: Didn't try. I just had the following: /q [INFO] Disconnecting from IRC. Click close again to exit now. /q [INFO] Disconnecting from IRC. Click close again to exit now. [ERROR] Internal error dispatching command "quit". [ERROR] Not connected. Expected result: Maybe I shouldn't have typed /q twice, but ChatZilla should have quit anyway. Additional info: The system was *extremely* sluggish due to heavy RAM & swap use by a different process. How sluggish? There was at times a noticeable delay between hitting CapsLock or NumLock and seeing the light go on or off. Don't ask how long between hitting the key for a printable character and seeing it appear onscreen.
P.S. CapsLock/NumLock delay length: a few tenths of a second. It's a USB keyboard but not wireless.
Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 ID:20140206003001 c-c:2e4699e14f86 m-c:1e9f169c9715 cChatZilla 0.9.90.1 Had it again today with only one /q ChatZilla had been disconnected for hours while I was away because it was waiting on a "wrong certificate" dialog. (The certificate was for *.freenode.net and, after a ping timeout, it was trying to connect to chat.eu.freenode.net which uses the same servers). I finally accepted the certificate but cZ did not reconnect. I typed /reconnect-all but AFAICT ChatZilla did not react. Typing /quit gave the same error as in comment #0 without the [INFO] message. The only way (that I have found) to reconnect ChatZilla consists of closing it, not by /quit but by clicking the [X] button at top-right of its window, then starting it afresh. Of course any (channel etc.) history is lost unless it was being logged, and in the latter case it can be read with a text editor or pager but AFAIK not with ChatZilla itself. This occurrence of the bug is for cZ in SeaMonkey 2.27a1 (Toolkit 30.0a1) while comment #0 was in Firefox 17 ESR. Same cZ version AFAIK. Not sure if it's worth setting tracking flags for the browser; there are none available in this bug for ChatZilla itself. I've also had similar errors with the /reconnect and /reconnect-all commands but I forgot to mention them in this bug, and now the details of how they happened are forgotten.
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.