From: SourceForge.net <no...@so...> - 2012-02-05 12:38:58
|
Bugs item #3483380, was opened at 2012-02-02 14:36 Message generated for change (Comment added) made by pipping You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3483380&group_id=88346 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Elias Pipping (pipping) Assigned to: Magnus Henoch (legoscia) Summary: groupchat buffer keeps popping up Initial Comment: With the current git HEAD, for at least one of my jabber contacts, an unrequested group chat buffer will appear almost immediately after I open a regular buffer for that contact. if i close the groupchat buffer, it will not reappear as long as the regular buffer stays open. If I delete the regular buffer and open create it anew, the groupchat buffer reappears, too. The problem is reproducible for that contact. version 0.8.0 does not have it. ---------------------------------------------------------------------- >Comment By: Elias Pipping (pipping) Date: 2012-02-05 04:38 Message: (since i didn't get a mail that notified me of the attachment i just added, i'm making it explicit here) ---------------------------------------------------------------------- Comment By: Elias Pipping (pipping) Date: 2012-02-05 04:37 Message: they don't seem too eager to tell anyone anything. there's a good chance they're running ejabberd, though. ---------------------------------------------------------------------- Comment By: Magnus Henoch (legoscia) Date: 2012-02-05 01:57 Message: Right, I found the problem. In jabber-roster-ret-action-at-point, we try to DTRT, i.e. open a chat buffer if the roster item is a contact and a groupchat buffer if the roster item is a chatroom. Normally, jabber.el will refuse to open a groupchat buffer if the JID is not a chatroom (as determined by disco), but your contact's server returns a feature-not-implemented error in response to the disco info request. Since at least one MUC server actually does that (ejabberd's mod_irc), jabber.el will give it the benefit of the doubt and open a groupchat buffer anyway... So... the right answer is probably to make RET in a roster buffer open a groupchat only if the JID actually says it's a groupchat, disabling the feature-not-implemented hack for this case, so you'd have to join non-compliant rooms with an explicit M-x jabber-muc-join. Out of interest, could you check what server this is? I.e. M-x jabber-get-version or M-x jabber-get-disco-info on HIS_HOST. ---------------------------------------------------------------------- Comment By: Elias Pipping (pipping) Date: 2012-02-03 09:51 Message: I replaced the: * name and host of that contact with HIS_NAME@HIS_HOST, * my name and host with MY_NAME@MY_HOST, and * my IP with MY_IP * my password with PASSWORD in the log. I also stripped all messages related to other contacts. The result is attached; ---------------------------------------------------------------------- Comment By: Magnus Henoch (legoscia) Date: 2012-02-03 08:39 Message: Sounds like an incoming message is incorrectly treated as a groupchat message. Could you set jabber-debug-log-xml to t and paste messages from that contact here? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=586350&aid=3483380&group_id=88346 |