Bug 574253 - empathy leaves status as "Away" after unlocking screen
Summary: empathy leaves status as "Away" after unlocking screen
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 614514 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-16 22:43 UTC by Mike Bonnet
Modified: 2011-06-27 15:11 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:11:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
A screenshot of empathy showing the green "Available" circle while the status shows "Away" (37.71 KB, image/png)
2010-03-16 22:43 UTC, Mike Bonnet
no flags Details

Description Mike Bonnet 2010-03-16 22:43:38 UTC
Created attachment 400589 [details]
A screenshot of empathy showing the green "Available" circle while the status shows "Away"

Description of problem:
After unlocking the screen, empathy leaves my status as "Away", even though it puts a green circle next to me (instead of the red triangle that should be shown if I am actually away).  I need to manually select "Available" from the status dropdown to get it to not show "Away".

Version-Release number of selected component (if applicable):
empathy-2.28.2-2.fc12.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Lock screen with Ctrl-Alt-L or leave yourself idle until the screensaver kicks in.
2. Unlock the screen.
3. Note that your status is "Away" instead of "Available", but a green circle is shown.
  
Actual results:
Status is "Away" instead of "Available".

Expected results:
Status is "Available".

Additional info:

Comment 1 Brian Pepple 2010-07-14 16:20:06 UTC
*** Bug 614514 has been marked as a duplicate of this bug. ***

Comment 2 Mike Bonnet 2010-07-14 16:38:44 UTC
I've determined that this only happens when one of the accounts I'm logged into is a Yahoo account.  If I'm not logged into Yahoo, none of my other accounts (AIM, GTalk) have this problem.

Note that this continues to happen on F13 as well.

Comment 3 Brian Pepple 2010-07-14 17:02:50 UTC
(In reply to comment #2)
> I've determined that this only happens when one of the accounts I'm logged into
> is a Yahoo account.  If I'm not logged into Yahoo, none of my other accounts
> (AIM, GTalk) have this problem.
> 
> Note that this continues to happen on F13 as well.    

Hmmm, that explains why I haven't been able to reproduce this bug. ;-)

Comment 4 Assen Totin 2010-07-15 07:25:49 UTC
Hi,

Same problem on i686 with a single ICQ account. As far as I remember, same account and same machine didn't have this problem on F12. 

WWell,

Comment 5 Bug Zapper 2010-11-03 19:27:46 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Mike Bonnet 2010-11-03 19:58:26 UTC
This still happens on F13.

I've noticed that if my desktop locks itself due to inactivity, I will be marked Available when I unlock my desktop (as I should be).  However, if I lock my desktop manually with Ctrl-L, then I'm always left Away when I unlock the desktop.

Comment 7 Bug Zapper 2011-06-02 16:08:24 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2011-06-27 15:11:28 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.