Community
Participate
Working Groups
Build ID: I20070621-1340 Steps To Reproduce: 1. Try to connect with a registered nickname, supplying wrong password. 2. Observe server response: "ERROR: 433,Nickname is already in use." 3. Observe server response disconnecting the IRC client: "ERROR: Closing Link: 127.0.0.1 (Connection Timed Out)" More information:
This is a small bug that is suitable for bugday IMHO. I'm interested in working on this bug on Eclipse Bug Day (July 27 2007)
(In reply to comment #1) > This is a small bug that is suitable for bugday IMHO. > > I'm interested in working on this bug on Eclipse Bug Day (July 27 2007) > It's all yours...thanks. I'm not sure I understand what the correct/expected behavior is though...shouldn't connect be refused for wrong password?
Current situation doesn't allow you to kill your ghost when this happens. I think the expected behaviour should be appending an underscore and/or a random number to keep you connected with a different nick as other IRC clients do.
Yeah, your nick should be switched with something else. The appending of an underscore's usually how it's done.
Changing title to reflect change of design implied by comment #3.
changing target milestone
Created attachment 135068 [details] Create ghost nick in the case nickname is already in use
Comment on attachment 135068 [details] Create ghost nick in the case nickname is already in use Hello buddies, I told to CCalli that I would try do solution to problem. So I found it. Now is similar XCHAT when you connected and your nickname is already in use, So will connect a ghost nick, adding underscore. I commented code. In the case doubt/suggestion please tell me. Check please!!! Any help would be most welcome... -Razec
Resolving as wontfix due to limited resources. If contributors or committer resources become available for additional work in this area then please reopen.
