Bug 149092 - nick rename not handled correctly in jabber multi user chat
Summary: nick rename not handled correctly in jabber multi user chat
Status: CONFIRMED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-21 23:02 UTC by Adrian Friedli
Modified: 2021-03-09 22:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Friedli 2007-08-21 23:02:06 UTC
Version:           0.12.5 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-4 (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-1-686

When changing the nickname in a jabber multi user chat (via right-clicking the channel's entry in the list) a new entry in the list appears but the original one is still there.

An example:
I join a groupchat with the nick foo.
I change my nick to bar, bar appears on the list and foo is still there but not functional.
I change my nick to baz, bar gets renamed on the list to baz but foo is still there.
I change back my nick from baz to foo, baz gets removed from the list and foo gets responsive again.

Another issue is that nickname highlightling always works for the original nickname (foo in the example above)
Comment 1 Dominik Tritscher 2008-07-28 20:38:27 UTC
I can confirm that using kopete 0.50.80 from KDE4.1RC1 Kubuntu packages.
I also noticed a difference in the naming schema of the duplicate entries:
The original was foo@conference.jabber.org, the renamed one was foo@conference.jabber.org/bar, asuming the original nick was foo, the new one bar.
Comment 2 Justin Zobel 2021-03-09 22:40:50 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.