Adium 1.0 fails silently to join Jabber group chat

[rbruels]

Almost the same problem as this ticket:

 http://trac.adiumx.com/ticket/3678

But with Adium 1.0. Occurred with the final beta, too. Did not try before that.

Joining a Jabber group chat using Adium 1.0 fails with no feedback. I can connect to a Jabber server. I do NOT receive invitations to Jabber group chat.

I pull up the Join Group Chat dialog, I enter the chat room name and hit enter (letting Adium autofill the Server field): the dialog box disappears, nothing else happens -- no extra cpu activity, no disk access, no network activity, no memory usage changes. I try same plus entering my username as the handle. No difference. I also enter my username@servername as my handle. Still no change.

Special configuration bits: - port 5223 - force old-style SSL on - no proxy - group chat was created on internal Jabber server via iChat, and invites are also coming from iChat

Console reports nothing out of the ordinary.

[rbruels]

Er, obviously title should be Adium *1.0* fails... was copying bits from the previous ticket.

[rbruels]

I'm dumping the AILog() calls for you. This is after I do "Join Group Chat", fill in the room name, then click "Join".

The server domain name changed to MYFAKEDOMAIN.com to protect the innocent...

2007-02-09 17:09:27.339 Adium[25491] 17:09:27: <DCJoinChatWindowController: 0x8fd21c0>: _selectPreferredAccountInAccountMenu: <AIAccountMenu: 0x57e320>: menuItem for <ESGaimAIMAccount:8608220 1>:bruelsatcu is <MenuItem: 0x579c50 BruelsAtCU>
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: Creating chatWithName:MyTestRoom@ichatserver.MYFAKEDOMAIN.com onAccount:<ESGaimJabberAccount:8608010 5>:bruelsry@ichatserver.MYFAKEDOMAIN.com chatCreationInfo:{
    handle = "bruelsry@ichatserver.MYFAKEDOMAIN.com"; 
    room = MyTestRoom; 
    server = "ichatserver.MYFAKEDOMAIN.com"; 
}
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: chatWithName MyTestRoom@ichatserver.MYFAKEDOMAIN.com existing --> (null)
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: [AIChat: 572df0 initForAccount]
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: chatWithName:MyTestRoom@ichatserver.MYFAKEDOMAIN.com onAccount:<ESGaimJabberAccount:8608010 5>:bruelsry@ichatserver.MYFAKEDOMAIN.com added <<<AIChat: 0x572df0>:<new>>> [<NSCFSet: 0x531400> (<AIChat: 0x9124ec0>:TechPubsDelivery@ichatserver.MYFAKEDOMAIN.com.0, <AIChat: 0x572df0>:<new>)]
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: gaim openChat:<AIChat: 0x572df0>:MyTestRoom@ichatserver.MYFAKEDOMAIN.com.1 for MyTestRoom@ichatserver.MYFAKEDOMAIN.com.1
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: Creating a chat.
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: Danger, Will Robinson! password is in the proto_info but can't be found in {
    handle = "bruelsry@ichatserver.MYFAKEDOMAIN.com"; 
    room = MyTestRoom; 
    server = "ichatserver.MYFAKEDOMAIN.com"; 
}
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: In the event of an emergency, your GHashTable may be used as a flotation device...
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: (Libgaim: jabber) Sending (ssl): <presence to='mytestroom@ichatserver.MYFAKEDOMAIN.com/bruelsry@ichatserver.MYFAKEDOMAIN.com'><status>yarrrr</status><priority>1</priority><c xmlns='http://jabber.org/protocol/caps' node='http://gaim.sf.net/caps' ver='2.0.0'/><x xmlns='http://jabber.org/protocol/muc'/></presence>
2007-02-09 17:09:39.010 Adium[25491] 17:09:39: chatWithName MyTestRoom@ichatserver.MYFAKEDOMAIN.com created --> <AIChat: 0x572df0>:MyTestRoom@ichatserver.MYFAKEDOMAIN.com.1

Following this, Adium does nothing -- no window shows up, no response whatsoever.

In the event of an emergency, I'll be one running away screaming. :P

[rbruels]

Regression testing: I can create/join the room on iChat, no problems whatsoever

[rbruels]

I just installed 1.0.1 today. Small behavioral difference: when I join the "default" chosen server -- in the example above, it would now be conference.ichatserver.MYFAKEDOMAIN.com -- the chat window actually spawns. I don't believe it's actually connecting to our valid chat servers (because I don't think that the server conference.ichatserver.MYFAKEDOMAIN.com actually exists), but I can comment on that for sure later.

Whenever I try to spawn another chat using "ichatserver.MYFAKEDOMAIN.com" or even (this is weird) explicitly typing out "conference.ichatserver.MYFAKEDOMAIN.com", I get the symptoms I've detailed with this trac ticket.

[jas8522]

Still a problem with 1.0.2?

[jas8522]

Closing due to inactivity.