Bug 702335 - gnome3 marking user as away after 5 seconds
Summary: gnome3 marking user as away after 5 seconds
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 11:20 UTC by Andreas Bierfert
Modified: 2011-06-06 20:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-06 20:35:45 UTC
Type: ---


Attachments (Terms of Use)

Description Andreas Bierfert 2011-05-05 11:20:24 UTC
Description of problem:
I am marked as 'Away' as soon as I let the mouse rest (say about 5 seconds). This makes e.g. g-screensaver kick in sets the status in empathy.

Version-Release number of selected component (if applicable):
gnome-shell-3.0.1-2.fc15.x86_64
gnome-screensaver-3.0.0-1.fc15.x86_64
empathy-3.0.1-2.fc15.x86_64

How reproducible:
Always.


Steps to Reproduce:
1. Log into gnom3 on up-to-date f15 system (updates-testing).
2. Wait 5 seconds.
  
Actual results:
User is marked away (as can be seen in the gnome-shell bar icon next to the user name), screensaver kicks in, empathy status is changed.

Expected results:
Being marked as away should happen after some more time (e.g. minutes or so). There should be an option in the controlcenter stuff for this somewhere.

Comment 1 Andreas Bierfert 2011-06-06 17:32:37 UTC
Still present on today's rawhide...

Comment 2 Andreas Bierfert 2011-06-06 20:35:45 UTC
I did some digging: For some reason org.gnome.desktop.session.idle-delay was set to 5 seconds. I am sure that I did not do this myself as I used dconf-editor after discovering this issue. 

Maybe this was caused by upgrading my system from f14->f15 sometime during the then f15-rawhide cycle?!


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