headers
Mandar Mitra | 18 Oct 2011 10:23
Picon

jabber-groupchat

I've recently upgraded to emacs-jabber-0.8.90 running under emacs-23.2
(Ubuntu 11.04) and noticed the following:

when I hit return on a name in jabber-roster, two buffers are opened:
one is the normal chat buffer, while the other has a name of the form
jabber-groupchat-xyz.

I'm not sure why this second buffer is coming up. It's easy enough to
kill the buffer, but is this a bug or a feature?

Thanks,
Mandar.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Permalink | Reply |
headers
Terechkov Evgenii | 18 Oct 2011 15:31
Picon

Re: jabber-groupchat

On Tue, 18 Oct 2011 13:53:13 +0530, Mandar Mitra <mandar.mitra <at> gmail.com> wrote:
> I've recently upgraded to emacs-jabber-0.8.90 running under emacs-23.2
> (Ubuntu 11.04) and noticed the following:
> when I hit return on a name in jabber-roster, two buffers are opened:
> one is the normal chat buffer, while the other has a name of the form
> jabber-groupchat-xyz.
> I'm not sure why this second buffer is coming up. It's easy enough to
> kill the buffer, but is this a bug or a feature?

It was conceived as a feature, but in your case it seems as bug :-)

Please set jabber-debug-log-xml to t and send XML log (or a link to
it) here.
--

-- 
                                                WBR, Terechkov
                                                Evgenii.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Permalink | Reply |
headers
Mandar Mitra | 18 Oct 2011 17:16
Picon

Re: jabber-groupchat

Hi,

Thanks for your quick response!

> It was conceived as a feature, but in your case it seems as bug :-)

If you could explain the intended use, maybe I can find a use for this
feature :).

> Please set jabber-debug-log-xml to t and send XML log (or a link to
> it) here.

There are a very large number of <presence>...</presence> blocks, and a 
few <iq> blocks. Do you really want to see all of this? Or should I look
for a specific pattern?

Thanks again,
Mandar.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Permalink | Reply |
headers
Terechkov Evgenii | 18 Oct 2011 17:47
Picon

Re: jabber-groupchat

On Tue, 18 Oct 2011 20:46:30 +0530, Mandar Mitra <mandar.mitra <at> gmail.com> wrote:

> > It was conceived as a feature, but in your case it seems as bug :-)
> If you could explain the intended use, maybe I can find a use for this
> feature :).

Intended usage is enable to enter any chatroom in roster whith just
<return> (you can add any JID-s in roster, MUC-s too). I use this
feature and unable to reproduce this bug.

> > Please set jabber-debug-log-xml to t and send XML log (or a link to
> > it) here.
> There are a very large number of <presence>...</presence> blocks, and a 
> few <iq> blocks. Do you really want to see all of this? Or should I look
> for a specific pattern?

Look for stanzas like this:

<!-- sending <at> 2011-10-18T13:00:46Z: -->
<iq to="YOUR <at> CONTACT.JID" type="get" id="emacs-iq-XXXXX.XXXXX.XXXXXX">
  <query xmlns="http://jabber.org/protocol/disco#info" nil=""/>
</iq>
<!-- sending <at> 2011-10-18T13:00:46Z: -->
<presence to="YOUR <at> CONTACT.JID/YOUR_NICK">
  <x xmlns="http://jabber.org/protocol/muc"/>
  <status>YOUR_STATUS_HERE</status>
  <nil/>
  <priority>YOUR_PRIORITY_HERE</priority>
  <x xmlns="vcard-temp:x:update">
    <nil/>
(Continue reading)

Permalink | Reply |
headers
Mandar Mitra | 18 Oct 2011 18:04
Picon

Re: jabber-groupchat

I hit <return> on the first contact (bandyopadhyay.ayan <at> gmail.com) and got
two buffers. Here's the relevant bit from the log:

I guess the third line is an indicator? It says protocol/muc, which is
perhaps why I'm getting the groupchat buffer?

<!-- sending <at> 2011-10-18T16:01:54Z: -->
<presence to="bandyopadhyay.ayan <at> gmail.com/mandar.mitra">
  <x xmlns="http://jabber.org/protocol/muc"/>
  <nil/>
  <show>xa</show>
  <priority>10</priority>
  <x xmlns="vcard-temp:x:update">
    <photo>91382fab64ba8e85a798842fe51d4ad67e2e2740</photo>
  </x>
</presence>
<!-- + -->

I'd greatly appreciate any suggestions on what might be wrong with my
setup. Thanks!
Mandar.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Permalink | Reply |
headers
Terechkov Evgenii | 18 Oct 2011 18:25
Picon

Re: jabber-groupchat

On Tue, 18 Oct 2011 21:34:43 +0530, Mandar Mitra <mandar.mitra <at> gmail.com> wrote:

> I hit <return> on the first contact (bandyopadhyay.ayan <at> gmail.com) and got
> two buffers. Here's the relevant bit from the log:
> I guess the third line is an indicator? It says protocol/muc, which is
> perhaps why I'm getting the groupchat buffer?

Yes, it is indicator, but for real-person JID's (not MUC-s) XMPP servers
should return error in reply to such stanza, AFAIR. Wrong answer from
your server is the only way I see here to lead to your case.

> <!-- sending <at> 2011-10-18T16:01:54Z: -->
> <presence to="bandyopadhyay.ayan <at> gmail.com/mandar.mitra">
>   <x xmlns="http://jabber.org/protocol/muc"/>
>   <nil/>
>   <show>xa</show>
>   <priority>10</priority>
>   <x xmlns="vcard-temp:x:update">
>     <photo>91382fab64ba8e85a798842fe51d4ad67e2e2740</photo>
>   </x>
> </presence>
> <!-- + -->

It is only only one stanza, not entire conversation with your server.
Please specify your value of jabber-muc-disable-disco-check variable and
step throught four steps from my previous message to capture full trace.

--

-- 
                                                WBR, Terechkov
                                                Evgenii.
(Continue reading)

Permalink | Reply |

Gmane