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 660500 - Empathy status always away as I log in
Empathy status always away as I log in
Status: RESOLVED DUPLICATE of bug 659021
Product: gnome-shell
Classification: Core
Component: telepathy
3.2.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Shell Telepathy maintainer(s)
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-29 17:21 UTC by nierro
Modified: 2011-09-30 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nierro 2011-09-29 17:21:35 UTC
As I said, my empathy status is always away when I log in gnome-shell 3.2.
And everytime I have to set to available, but then, on one hand my gfire account won't log in, on the other hand, when I swith off as available, then boot again, it seems to forget my status and change it to away.
Only if i run empathy, it seems to fix everything and all my accounts are set to avaiable.
I can't understand, very annoying bug.
Hope this can be fixed!
Thanks
Comment 1 Guillaume Desmottes 2011-09-30 09:22:58 UTC
Sounds like a Shell bug.
Comment 2 Florian Müllner 2011-09-30 10:44:42 UTC
Away or offline?
Comment 3 nierro 2011-09-30 14:07:24 UTC
Well, on the gnome-menus I only have available and unavailable, and it is set on unavailable. While on empathy i am offline.
Sorry for my bad english, hope you can understand me well!
Comment 4 Florian Müllner 2011-09-30 14:17:31 UTC
(In reply to comment #3)
> Well, on the gnome-menus I only have available and unavailable, and it is set
> on unavailable. While on empathy i am offline.

Thanks - the user menu does display other statuses as well (e.g. "Away") when something else (e.g. Empathy) sets this status, that's why I was asking.

Currently we don't remember the last status, so unavailable/offline is the expected status. I agree we should remember the status ...

*** This bug has been marked as a duplicate of bug 659021 ***