#762 new defect

Away status is inaccurate when contact is signed into Jabber multiple times

Reported by: Daniel Egeberg <daniel.egeberg@…> Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 3.0.1
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro: Gentoo


When a contact is signed into multiple Jabber resources simultaneously, the status that BitlBee provides for the contact is sometimes inaccurate.

Example: Contact is signed into GTalk using Pidgin and the Gmail web client. The status is 'online' in Pidgin, but 'away' in Gmail. BitlBee marks this contact as away where I would have expected the opposite.

Attachments (0)

Change History (4)

comment:1 Changed at 2011-03-06T21:45:00Z by anonymous

Hmm, what do other clients do here? I suppose most of them just show all statuses in their tooltips, but what do they do with the buddy status icon?

BitlBee, IIRC, picks the highest-priority resource and uses that one for the away status/msg.

comment:2 Changed at 2011-03-07T08:09:26Z by Daniel Egeberg <daniel.egeberg@…>

In the above example, both Pidgin and the Google Talk app on Android would report the contact as online.

comment:3 Changed at 2011-06-12T09:22:42Z by wilmer

(Ugh. I could've responded a bit earlier..)

Interesting. Do they show the other away state at least somewhere? And they really do this even if the non-away one has a lower priority value? I wonder if this is something I've missed in the RFC or if this is their idea (and quite likely not a bad idea actually).

comment:4 Changed at 2013-04-17T07:55:57Z by Anthony Ginepro <rapiere@…>

Is there a way to choose "bitlbee's away check" behavior ? Especially since Google Talk is used on mobile phones, most of my friends seem away because they are on their phone but not in GMail, in this situation picking online status from any account would be more accurate. Thanks

Modify Ticket

as new The owner will remain wilmer.

Add Comment

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

Note: See TracTickets for help on using tickets.