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 667813 - GNOME Shell says my contact went offline when he is just away
GNOME Shell says my contact went offline when he is just away
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: telepathy
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Shell Telepathy maintainer(s)
gnome-shell-maint
: 663851 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-01-12 20:44 UTC by Jean-François Fortin Tam
Modified: 2012-01-13 16:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
telepathyClient: handle ExtendedAway as Away and not Offline (1.55 KB, patch)
2012-01-13 10:18 UTC, Guillaume Desmottes 		committed Details | Review

Description Jean-François Fortin Tam 2012-01-12 20:44:01 UTC 
It seems that whenever someone I'm chatting with becomes Away, the shell says that person is now offline, which is a lie.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-01-12 20:45:29 UTC 
We treat "Extended Away" as offline for some reason. It's certainly a mismatch between our terms and the terms that Empathy use.
Comment 2 Guillaume Desmottes 2012-01-13 10:18:36 UTC 
Created attachment 205174 [details] [review]
telepathyClient: handle ExtendedAway as Away and not Offline
Comment 3 Xavier Claessens 2012-01-13 10:24:07 UTC 
+1
Comment 4 Milan Bouchet-Valat 2012-01-13 15:21:59 UTC 
This was already suggested, but people were not sure it was the right thing. I guess you can tell...

*** This bug has been marked as a duplicate of bug 663851 ***
Comment 5 Guillaume Desmottes 2012-01-13 15:28:28 UTC 
Attachment 205174 [details] pushed as 6cdb1bd - telepathyClient: handle ExtendedAway as Away and not Offline
Comment 6 Milan Bouchet-Valat 2012-01-13 15:39:43 UTC 
So, should bug 663851 be marked as duplicate of this one rather?
Comment 7 Florian Müllner 2012-01-13 15:59:55 UTC 
*** Bug 663851 has been marked as a duplicate of this bug. ***
Comment 8 Florian Müllner 2012-01-13 16:00:56 UTC 
(In reply to comment #6)
> So, should bug 663851 be marked as duplicate of this one rather?

Yeah, there's no point in leaving that open.