Bug 1038657

Summary: IM status set to "Away" when screen is locked, and never reset when unlokcked
Product: [Fedora] Fedora Reporter: Phil Mayers <p.mayers>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 14:00:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Phil Mayers 2013-12-05 15:23:25 UTC
Description of problem:

When I lock the screen under the default F18 / Gnome3 desktop, Empathy sets my XMPP accounts to "Away". When I unlock, it never changes them back.

Version-Release number of selected component (if applicable):

empathy-3.6.4-3.fc18.x86_64
telepathy-gabble-0.16.7-1.fc18.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Check status is "Available"
2. Lock screen
3. Unlock screen

Actual results:

Status is now "Away"

Expected results:

Status should go back to "Available"

Additional info:

I think this is a recent thing - perhaps with a recent update?

Comment 1 Phil Mayers 2013-12-20 14:00:11 UTC
Can no longer reproduce this - closing

Comment 2 Fedora End Of Life 2013-12-21 14:48:14 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.