Joining named chatrooms mostly broken with libpurple

[dukrat]

Behavior: If you set up a jabber conference (chat add 0 conf@… #conf) and set it to autojoin (channel 1 set auto_join='true'), when you rejoin the server channel #conf pops up with @root and @user but just stays that way. A short time later channel #chat_000 pops up properly connected to the conference.

Expected behavior: Only #conf should pop up and it should be properly connect to the conference.

[Wilmer van der Gaast <wilmer@…>]

Are you using libpurple?

[anonymous]

Replying to Wilmer van der Gaast <wilmer@…>:

Are you using libpurple?

Yes, sorry for not mentioning it before. This is with libpurple compiled version.

[wilmer]

As expected. Yes, chatrooms don't work well with libpurple. Libpurple doesn't do asynchronous joins very nicely and I haven't taken the time to try to fix it.

Is there any reason why you're using libpurple?

[anonymous]

Replying to wilmer:

As expected. Yes, chatrooms don't work well with libpurple. Libpurple doesn't do asynchronous joins very nicely and I haven't taken the time to try to fix it.

Is there any reason why you're using libpurple?

Mostly for zephyr support. I suppose I can install two versions, use one server for zephyr and another for irc.

[Wilmer van der Gaast <wilmer@…>]

That might work. If you compiled your own, you can try modifying the configure script and remove the line that says jabber=0. I think that should work.

[anonymous]

Replying to Wilmer van der Gaast <wilmer@…>:

That might work. If you compiled your own, you can try modifying the configure script and remove the line that says jabber=0. I think that should work.

Okay, I decided to go with your suggestion and make a hybrid compile. I used all of your modules in addition to libpurple. So far I haven't seen anything break, but I have only tried jabber.

[Wilmer van der Gaast <wilmer@…>]

Yep, it should work. Only the other way around (trying to use a libpurple module for a protocol that is also compiled into BitlBee) might cause troubles.

[drew666@…]

This would be nice to have working -- but I can stop using LibPurple.

[anonymous]

I stopped using LibPurple, but I still have this problem.

[anonymous]

Perhaps the version of Ubuntu I have uses an older Bitlbee with this bug.

bitlbee -V

BitlBee 3.0.4+bzr855-1 API version 030004

[wilmer]

But what problem are you having exactly? Since this is an unrelated problem, can you open a new bug for it?

[drew666@…]

Sorry, the problem was with libpurple after all. Fixed it when I switched, I just needed to restart.

Thanks for Bitlbee, it's working great now.

[dkowis+bitlbee@…]

I have this problem as well, because I have to use libPurple.

Maybe an unrelated bug, but if I many connections to a jabber chatroom (like I log in from my phone, and from bitlbee) I don't see in bitlbee any communcations from me on my phone, perhaps because they're both the same jabber account. It works great with libPurple, but I now have the problem of #chat_000 instead of #named_room.

Additionally I had a problem where the connection to the named chatroom would keep disconnecting and reconnecting, and not showing up all the users. It works much more reliably with libPurple. Thanks!

[dx]

I believe this is fixed with this commit:

​https://github.com/bitlbee/bitlbee/commit/a3019499665384a3dcbbc11016d256e6d4dcd26c