After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 369330 - Online status displays away although one resource is available
Online status displays away although one resource is available
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
0.18
Other All
: Normal normal
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-02 10:08 UTC by Alexander Brausewetter
Modified: 2006-11-26 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Brausewetter 2006-11-02 10:08:59 UTC
Please describe the problem:
When a jabber contact is logged in with more than one resource (e.g. x@example.org/Home, x@example.org/Work) and only one of them is available, Gossip does not favour the online connection and displays the contact as away.

When looking at the contact info, Gossip displays both resources and confirms that one is online and the other one is away.

Steps to reproduce:
1. Add a contact
2. Connect to the contact accout with two resources, set one to status away
3. The described behaviour will occur


Actual results:
The contact is shown as away, although it is available with one resource

Expected results:
Gossip should display the best status available, that is in order: available, busy, away.

Does this happen every time?
yes

Other information:
Comment 1 Robert Mibus 2006-11-23 23:01:11 UTC
This causes me problems with Google Talk users who log in multiple times. When I initiate a chat, Gossip seems to use the resource which sent the most recent presence, rather than the "most available" resource.

IMHO, resource detection should use priority/status/recentness in that order.
Comment 2 Martyn Russell 2006-11-24 09:19:16 UTC
Yes, this is known about. I need to fix this.
Comment 3 Martyn Russell 2006-11-26 14:03:42 UTC
Thanks, I have just fixed this.