[Pidgin] #4062: MSN nick keeps switching randomly (or so it seems)

[Pidgin]

#4062: MSN nick keeps switching randomly (or so it seems)
-----------------------+----------------------------------------------------
  Reporter:  atourino  |       Owner:  khc          
      Type:  defect    |      Status:  closed       
  Priority:  minor     |   Milestone:  2.3.1        
 Component:  MSN       |     Version:  2.3.0        
Resolution:  fixed     |    Keywords:  nick changing
   Pending:  0         |  
-----------------------+----------------------------------------------------
Comment (by wpliao):

 I am suffering from the same problem here, version 2.3.0, where my
 friendly name displayed in my chat window has been randomly changed to one
 of my contact's, and it seems to be the person who has recently changed
 their status to online (but I could be wrong).

 While the other person engaged in the chat does not see the incorrect
 friendly name (i.e. the other person sees the what I have previously
 entered), the incorrect friendly name is stored in the log file and also
 shows up as the default value in the input box when I attempt to update my
 friendly name.

 This means somewhere in the program it mistakenly adopts the incorrect
 name internally and globally in the program although the process to update
 the friendly name has not been initiated.

 The trick of using an alias for myself may work (it seems to work for the
 last couple hours, but there hasn't been anyone logging on during this
 time and will not be at this hour). However, setting an alias means I need
 to update my alias every time I change my friendly name (so I can see it
 in my own chat window), and I do not understand why I need to enter the
 same thing twice. Besides, I like to change my friendly name, which adds
 fun to messaging especially when the new name has a subtle meaning to the
 engaged conversation, but this is not fun if I don't see the friendly name
 myself.

 [[BR]]
 [[BR]]

 I do not quite understand why the status has been changed to closed,
 although a temporary work-around has been offered, the actual problem has
 not been fixed. I'd really appreciate if this bug can be reset to
 open/assigned, or, even better, if this bug can be fixed.

 Thanks to all.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4062#comment:2>
Pidgin <http://pidgin.im>
Pidgin