Open Bug 824843 Opened 7 years ago Updated 6 years ago
Client tries to steal other user's nickname in conversation
When you open a conversation with another user, click on the nickname button and select Change nickname, the client apparently tries to steal the nickname of the conversation partner. Instead of the usual prompt where one can change their nickname, following message appears in the conversation: === The nickname “NickName” is already in use, use the /nick command to pick a new one.
I can confirm this behaviour.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to Gryllida from comment #1) > I can confirm this behaviour. Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17a1 ID:20121219180903 c-c:68dcb9af22fb m-c:21195f52311c me too, and also on L64 trunk.
Hardware: x86 → All
Version: unspecified → Trunk
P.S. When in a query with NickServ (or ChanServ or MemoServ etc.) the message is different but the phenomenon is the same: NickServ Erroneous Nickname: Reserved for Services meaning cZ tried (and failed) to change its nick to "NickServ".
This is caused by the patch for Bug 450309, specifically the lines in static.js that define rv.nickname to be rv.userName.
Duplicate of this bug: 960396
You need to log in before you can comment on or make changes to this bug.