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

Pidgin trac at pidgin.im
Fri Feb 19 12:35:23 EST 2010


#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 Jade Knight):

 Still occurs with Pidgin 2.6.6.

 I don't tend to get randomly kicked from chats, but I occasionally find
 myself unable to join them.

 Random peculiarities:  I am sometimes able to join a DIFFERENT chat while
 remaining locked out of one, but not always.  I am usually able to join
 chats with different accounts also logged into Pidgin (I don't have to use
 a different client).  When I have one account in the room, and the other
 tries to join, all you get is the "left the room" message.

 When trying to join a chat unsuccessfully, this is what goes in the debug
 window:
 (09:21:28) oscar: Attempting to join chat room arena.
 (09:21:28) oscar: chatnav exists, creating room
 (09:21:28) oscar: created room: arena 16 0 64 1266600080 2000 50 1 22
 arena !aol://2719:10-16-arena

 And that's it.  I get no message of any sort.  It just won't join.
 Invitations don't help.

 Disabling the affected account and reenabling does '''not''' fix this
 problem for me.  Closing Pidgin entirely and then reopening it does not
 fix this problem for me.  I don't know what causes the problem, and I
 don't know how to work around it except to use a different SN whenever one
 can't get into a chatroom.

 I've tried signing off the problematic account in Pidgin and then signing
 on in Meebo once, and then inviting it to a chatroom, and the problem
 persists (or did the one time I tried this).

 This may suggest that the issue is related directly to the way the
 protocol handles things, but is there any way to work around this without
 switching SN's?

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


More information about the Tracker mailing list