#1068 closed defect (notabug)

Buddy list for Jabber server appears for only one Bitlbee instance

Reported by: sergiodj@… Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 3.2
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro: Fedora 17



I am seeing a strange behavior when using Jabber. I have two computers which run Bitlbee (same version, bitlbee-3.2-3.fc17.x86_64), and my contact list (buddy list) for this Jabber account only appears at one instance of Bitlbee. So if I connect to Bitlbee from the computer #1 first, and then from computer #2, my contacts will only appear on #1. And even if they send me a message, I only receive it from #1 (even though #2 reports that the connection to the Jabber server was successful). This is a pretty annoying behavior because I always have to check the first computer logged in to see if there are new messages.

For the record, I tested running Bitlbee on one machine and Pidgin on another, and everything was fine (i.e., I was able to see my contacts on both machines). I also use Gtalk on both machines, and this problem never occurred with it.

Attachments (0)

Change History (2)

comment:1 Changed at 2013-06-23T06:46:41Z by sergiodj@…

Hm, it seems (still not totally confirmed) that if I use a username like "" (instead of ""), Bitlbee is able to retrieve the buddy list on both instances. I still have to confirm this, though. (And BTW, if this is indeed true, it would be really good if Bitlbee assumed the last slash as default).

The code which prompted me to try this was:

And also the fact that Pidgin was displaying my user with the last slash appended, even though I had not set it.

comment:2 Changed at 2015-11-28T18:57:25Z by dx

Resolution: notabug
Status: newclosed

This is more of a server oddity than anything, about the way the 'resource' setting is used (the stuff after the slash, or the setting of the jabber bitlbee account).

The default value for that setting in bitlbee is 'BitlBee'. In most servers I've used, if you two bitlbees without changing that setting, the first connection gets kicked. In other cases, such as gtalk, the server changes the client's resource adding some garbage at the end, like "BitlBee245A222B".

Other clients weren't a problem because they use different resources.

Adding a slash at the end of the username means changing the resource to an empty string, which makes it different.

The same effect can be achieved with account jabber set resource whatever

(Somehow never noticed this ticket before, and i've gone through the ticket list many, many times. I blame the ticket right below it, which always catches my attention. Sorry!)

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.