Project

General

Profile

Bug #964

Nick Select Doesn't Update on Forced Nick Change

Added by MadCabbit over 11 years ago. Updated about 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/15/2010
Due date:
% Done:

0%

Estimated time:
Version:
0.6-pre
OS:
Windows

Description

On networks that force nick changes for registered nicks instead of kills, Quassel IRC's nick selector doesn't seem to detect it.

Say you're using MyNick, with alternates MyNick2 and MyNick3, and the current nick gets changed:

[NickServ] This nickname has been registered; you may not use it. Your nickname is now being changed to Guest163043354.

The selector still shows MyNick, and the drop down shows MyNick, MyNick2, and MyNick3. Trying to select MyNick to change back instead refreshes the selector, and in this case, Guest163043354 finally shows up, but doesn't change nicks back to MyNick. Selecting MyNick again finally works.

Version 0.6.1


Related issues

Related to Quassel IRC - Bug #1020: Wrong nickname when connecting to bouncerResolved2010-09-08

History

#1 Updated by xeross about 10 years ago

I am having the same issue with my bouncer inbetween, even when I do a /nick myself while Quassel is "desynchronized" it will not update the select, and the internal nickname. This might also be related to #1020

#2 Updated by TorrentialStorm about 10 years ago

Try my patch from #1020, that should also fix forced nick changes.

Also available in: Atom PDF