Bug 858033 - Hanging issues when enforcing locking
Hanging issues when enforcing locking
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-screensaver (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Ray Strode [halfline]
Desktop QE
Depends On:
Blocks: 670971
  Show dependency treegraph
Reported: 2012-09-17 16:21 EDT by Matthew Mosesohn
Modified: 2017-12-06 06:02 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-06 06:02:57 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Mosesohn 2012-09-17 16:21:43 EDT
Description of problem:
If you enforce certain policies to make gnome-screensaver lock after 10 minutes, the system hangs for several seconds while locking. 

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

How reproducible:

Steps to Reproduce:
1. Run these commands to enforce:
  #Add rule that screensaver must activate when system is considered idle
  gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type boolean --set /apps/gnome-screensaver/idle_activation_enabled "true"
  #Add rule that screensaver must lock screen when enabled
  gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type boolean --set /apps/gnome-screensaver/lock_enabled "true"
  #Add rule for 10 minute screensaver
  gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type int --set /apps/gnome-screensaver/idle_delay "10"
  gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type int --set /desktop/gnome/session/idle_delay "10"
  #Ensure no delay after screensaver before lock
  gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type int --set /apps/gnome-screensaver/lock_delay "0"
2. Log in
3. Wait 10 minutes for screensaver to engage
Actual results:
There is a significant period of time (3-5 seconds) where you can't input.

Expected results:
Immediate ability to unlock

Additional info:
If you set lock_delay to 1, the behavior is exacerbated.  You have to wait for screen to darken and then still another 10 seconds before the screensaver disables (no prompt though).

What is desired is the ability to prevent screensaver during the period where the screend darkens (first 5 seconds) and not enter a password, and not be hung up waiting.
Comment 2 RHEL Product and Program Management 2012-12-14 03:07:06 EST
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 Jan Kurik 2017-12-06 06:02:57 EST
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:


This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:


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