[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
URL:
  <http://savannah.nongnu.org/bugs/?37963>

                 Summary: No Buffer Created when Joining Python MUC using
Bitlbee.
                 Project: WeeChat
            Submitted by: oxseyn
            Submitted on: Thu 20 Dec 2012 02:36:00 PM GMT
                Category: None
                Severity: 3 - Normal
              Item Group: irc protocol
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name:
        Originator Email:
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 0.4.0-dev
                IRC nick: oxseyn

    _______________________________________________________

Details:

Weechat: Version: 0.4.0~dev+20121219~precise1
OS: Ubuntu 12.0.4.1 Desktop i386
Bitlbee: Version: 3.0.4+bzr855-1

FYI: This setup works with irssi w/ irssi-xmpp & bitlbee.

I'm using Bitlbee as a jabber (private company server) to IRC gateway.  I
connect to the jabber server without a problem.  I can see everyone connected
on the server and chat with them.  When they message me a new buffer is
created.

To add a Jabber MUC channel to bitlbee, I issue the following command
(relevant to bitlbee, not weechat, just being comprehensive):

/chat <account> <roomname>@<serveraddress> <localname>
This is executed successfully and it creates the local channel.

/join <localname>

This is executed, users on the server see me join the channel, but the buffer
is NOT created in weechat.  I think this has to do with the way that the
Jabber notification messages are received and parsed by weechat.  For all
intensive purposes I am in the server, there is just simply no buffer for me
to interact with.

/join <localname>
When I execute this command again I get an error message that I am already in
the channel.




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Follow-up Comment #1, bug #37963 (project weechat):

07:56:29 localhost <-- | PRIVMSG &bitlbee :chat list
07:56:29 localhost --> | :root!root@localhost PRIVMSG &bitlbee :Warning: The
 2chat 2 command was mostly replaced with the  2channel 2 command.
07:56:29 localhost --> | :root!root@localhost PRIVMSG &bitlbee : 0. &bitlbee,
control channel (joined)
07:56:29 localhost --> | :root!root@localhost PRIVMSG &bitlbee : 1. #malware,
chat channel
07:56:29 localhost --> | :root!root@localhost PRIVMSG &bitlbee :End of channel
list
07:56:33 localhost <-- | JOIN #malware
07:56:33 localhost --> | :root!root@localhost PRIVMSG #malware :From
conference server: This room is not anonymous.
07:56:35 localhost <-- | JOIN #malware
07:56:35 localhost --> | :root!root@localhost PRIVMSG &bitlbee :jabber -
Error: Already present in chat `[hidden email]'

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Follow-up Comment #2, bug #37963 (project weechat):

Discussion from IRC, just summarized here:

Seems that bitlbee didn't send a JOIN response, but still believes you've
joined the channel. If a JOIN response is /required/ from the server, then
this bitlbee version seems to not be protocol compliant and is hence at
fault.

Irssi seems to react differently and create the buffer on executing the /join
command, not receiving the JOIN response.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Update of bug #37963 (project weechat):

                Category:                    None => irc plugin            
                  Status:                    None => Need Info              
             Assigned to:                    None => flashcode              
                 Release:               0.4.0-dev => 0.3.9                  

    _______________________________________________________

Follow-up Comment #3:

Some news about this problem?
I think this is a Bitlbee problem, not WeeChat: any IRC server MUST sent a
JOIN for channel you have joined.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Update of bug #37963 (project weechat):

                  Status:               Need Info => Invalid                

    _______________________________________________________

Follow-up Comment #4:

This is not a WeeChat bug for me (unless you bring proof it is one!).

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Follow-up Comment #5, bug #37963 (project weechat):

I switched back to irssi (it works), but just revisted this issue yesterday
with updated software.

The same exact behavior occurs.
I add the chat in bitlbee, then issue the /join <channel> command in weechat -
I see my weechat/bitlbee client join the jabber MUC, but no buffer is created.
 The JID can send and receive private messages on the server, but any test
entered into the chat is never received on the weechant client (because the
buffer wasn't created).

I really wish I could get this to work, so I could switch over to using
weechat. :(

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Update of bug #37963 (project weechat):

                  Status:                 Invalid => Need Info              

    _______________________________________________________

Follow-up Comment #6:

Can you send a raw log (/server raw) of all messages sent from weechat to
bitlbee, and from bitlbee to weechat?
Does bitlbee send a "JOIN :#something" to your weechat ? If yes, then the
buffer should be opened by WeeChat. If this message is received and that
buffer is not opened, it's a bug.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Follow-up Comment #7, bug #37963 (project weechat):

No join message is sent to the client by the server.
A presence message for each person in the room is sent to the client (I
stripped all the personal information):

│08:24:17 xmlconsole | RX: <presence to="<username>@imserver/BitlBee"
from="<room>@<server>/<user>"><show>away</show><status>Away</status><c
xmlns="http://jabber.org/protocol/caps" node="http://pidgin.im/"
│                    | hash="sha-1" ver="DdnydQG7RGhP9E3k9Sf+b+bF0zo="/><x
xmlns="http://jabber.org/protocol/muc#user"><item
jid="<username>@<server>/<client>" affiliation="<affiliation>"
role="<role>"/></x></presence>

And a groupchat message:

│08:24:17 xmlconsole | RX: <presence to="<username>@<server>/<client>"
id="<id>" from="<room>@<server>/<nick>"><x
xmlns="http://jabber.org/protocol/muc#user"><item
jid="<username>@<server>/<client>"
│                    | affiliation="<affiliation>"
role="<role>"/></x></presence>

This works in irssi because it creates a buffer based on the /join command (a
buffer is created even if the room is not actually joined).

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev
Reply | Threaded
Open this post in threaded view
|

[bug #37963] No Buffer Created when Joining Python MUC using Bitlbee.

Eric L.-2
Update of bug #37963 (project weechat):

                  Status:               Need Info => Works For Me          

    _______________________________________________________

Follow-up Comment #8:

I just tested to join a MUC and it works fine for me, bitlbee sends the JOIN
:#channel as expected (and then buffer was created).

I'm using Bitlbee 3.2 under Debian (can you please try with this version?).

Here are the commands I used in &bitlbee buffer to create/join my MUC (0 is my
jabber account):


chat add 0 [hidden email]
/join #testseb


Here is the beginning of raw log in WeeChat when I join the channel (/server
raw):


bitlbee <-- | JOIN #testseb
bitlbee --> | :FlashCode!FlashCode@localhost JOIN :#testseb
bitlbee --> | :localhost MODE #testseb +t
bitlbee --> | :localhost 353 FlashCode = #testseb :@FlashCode @root
bitlbee --> | :localhost 366 FlashCode #testseb :End of /NAMES list
bitlbee --> | :localhost 332 FlashCode #testseb :BitlBee groupchat:
"[hidden email]".
            | Please keep in mind that root-commands won't work here. Have
fun!



    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37963>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/


_______________________________________________
Weechat-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/weechat-dev