[Pidgin] #1449: Can't join AIM chatrooms (only sometimes; Pidgin doesn't crash)

[Pidgin]

#1449: Can't join AIM chatrooms (only sometimes; Pidgin doesn't crash)
--------------------------------+-------------------------------------------
 Reporter:  Refinery            |        Owner:  MarkDoliner
     Type:  defect              |       Status:  new        
Milestone:                      |    Component:  AIM        
  Version:  2.0.1               |   Resolution:             
 Keywords:  AIM chat room join  |  
--------------------------------+-------------------------------------------

Comment(by VulpesFoxnik):

 Replying to [comment:30 ticktock]:
 > I, along with a lot of my friends who use Pidgin (2.5.5), have been
 having the same problem and it's very frustrating. We'll get disconnected
 from an AIM chatroom or have an error where Pidgin will crash and when we
 try to log back into the room nothing happens. If one person remains in
 the room and another person who has this problem tries to restart Pidgin,
 the person still in the room will get the "XXX has left the room" message
 every time the other person exits the program without them ever having
 been able to rejoin the room to begin with.
 >
 > When we get this error, we can't join ANY chat rooms - not just the one.
 But we are able to rejoin the same room (or any room) if we log on other
 screen names.
 >
 > It happens seemingly randomly, and sometimes it just fixes itself, but
 we don't know why. Restarting the computer/router/modem does nothing.
 >
 > This is the only thing that appears in the debug log on an unsuccessful
 attempt (standard login.messaging.aol.com for the server):
 >
 >
 > {{{
 > (23:42:53) oscar: Attempting to join chat room chaterror.
 > (23:42:53) oscar: chatnav exists, creating room
 > (23:42:55) oscar: created room: chaterror 4 0 64 1241926974 2000 39 1 22
 chaterror aol://2719:10-4-chaterror
 > }}}
 >
 >
 > It says it created the room, yet no window pops up and anyone currently
 in the chatroom will not see us join.
 >
 > on a successful attempt, we get something like this:
 >
 > {{{
 > (00:09:53) oscar: Attempting to join chat room jonsucks.
 > (00:09:53) oscar: chatnav exists, creating room
 > (00:09:53) gtkappbar: wnd_poschanging
 > (00:09:53) gtkappbar: wnd_poschanged
 > (00:09:53) gtkappbar: wnd_activate
 > (00:09:53) oscar: created room: jonsucks 4 0 64 1241928610 2000 39 1 22
 jonsucks aol://2719:10-4-jonsucks
 > (00:09:53) oscar: Connecting to FLAP server 205.188.179.20:5190 of type
 0x000e (00:09:53) oscar: Connecting to chat room aol://2719:10-4-jonsucks
 exchange 4 (00:09:53) dnsquery: Performing DNS lookup for 205.188.179.20
 > (00:09:53) dnsquery: IP resolved for 205.188.179.20
 > (00:09:53) proxy: Attempting connection to 205.188.179.20
 > (00:09:53) proxy: Connecting to 205.188.179.20:5190 with no proxy
 > (00:09:53) proxy: Connection in progress
 > (00:09:54) proxy: Connecting to 205.188.179.20:5190.
 > (00:09:54) oscar: connected to FLAP server of type 0x000e
 > (00:09:54) oscar: FLAP connection of type 0x000e is now fully connected
 > (00:09:54) oscar: inside chat_info_update (maxmsglen = 2000, maxvislen =
 1024) (00:09:55) util: Writing file prefs.xml to directory
 C:\Users\Mike\AppData?\Roaming\.purple
 > (00:09:55) util: Writing file
 C:\Users\Mike\AppData?\Roaming\.purple\prefs.xml
 > 00:09:56) gtkappbar: wnd_activate
 > }}}
 I can confirm that these symptoms also Exist in Debian 2.7.2

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