Bug 184108 - WLM (MSN) Nick Won't Change
Summary: WLM (MSN) Nick Won't Change
Status: RESOLVED DUPLICATE of bug 182366
Alias: None
Product: kopete
Classification: Applications
Component: WLM Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-12 06:53 UTC by Jeffery MacEachern
Modified: 2009-03-29 05:55 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 Jeffery MacEachern 2009-02-12 06:53:40 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Unlisted Binary Package

Steps to Reproduce:
Pull up the accounts list on the bottom of the Kopete contacts window, right-click on a WLM account, and attempt to change your Nick.
Expected Outcome:
Nick will be changed permanently, until such a time as you change it again.
Actual Outcome:
Nick does not change at all, as evidenced by lack of notification in chat windows, and checking your Nick in the same way that you set it.

Other Notes:
I only noticed this recently - possibly since the RC, but I'm not sure, as I wasn't aware of it for some time after the release of 4.2.0.  Also, I've noticed that when I use another client, such as Pidgin, or the official MS WLM client, my Nick in that client is set to whatever it last was /in that client/, even across machines.  However, when this bug first appeared, I noticed it because my Nick had reverted to one that I had used some time ago on a different computer/OS/client, and never in Kopete...  That may be a separate issue, but I thought it was worth mentioning, in the context of this bug.
Comment 1 Jeffery MacEachern 2009-03-16 09:17:31 UTC
It appears that my report is a duplicate of Bug #182366, which was fixed in 4.2.1.  Could someone please confirm, and close this bug if appropriate?
Comment 2 Matt Rogers 2009-03-29 05:55:19 UTC

*** This bug has been marked as a duplicate of bug 182366 ***