RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 816347 - On screenlock when the screen fades, pressing keys to prevent the lockout does not work
Summary: On screenlock when the screen fades, pressing keys to prevent the lockout doe...
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server
Version: 6.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
Depends On:
Blocks: 782183 842499
TreeView+ depends on / blocked
Reported: 2012-04-25 20:39 UTC by Simo Sorce
Modified: 2018-11-30 21:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-21 08:03:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0299 0 normal SHIPPED_LIVE xorg-x11-server bug fix and enhancement update 2013-02-20 20:35:47 UTC

Description Simo Sorce 2012-04-25 20:39:42 UTC
In 6.2 you can press a key when you see the screen starting fading for an impending screenlock.
With the beta packages (1.10.6-1.el6.i686) this doesn't work, and you are left watching a quite slow fade until you are brought to a screensaver unlock screen.

The cause might be the fix for rhbz#748704

Comment 2 Tomas Pelka 2012-04-25 20:54:52 UTC
I can remember that I saw this behavior as well, but not any more right now. Just FYI.

Comment 4 Adam Jackson 2012-04-26 14:33:50 UTC
Simo tested a patch for me, and it appears to have worked.  Writing this down so I don't forget:

This is indeed caused by:

* Mon Mar 19 2012 Adam Jackson <ajax> 1.10.4-14
- xserver-1.10.4-sync-revert.patch: Revert an edge-case change in IDLETIME
  that appears to be more wrong than right. (#748704)

That patch reverts two hunks from Xext/sync.c.  Those hunks would be correct, if they swapped places.

I don't believe this bug to be a blocker, inability to interrupt the screensaver is merely cosmetic.

Comment 8 Adam Jackson 2012-09-12 16:33:05 UTC
Upstream fix for this was:

commit 4a6f42dda00ba3b5616f8a86f0d4c9a652c7d9d4
Author: Adam Jackson <ajax>
Date:   Mon Jul 23 16:34:28 2012 -0400

    sync: Fix logic error from b55bf248581dc66321b24b29f199f6dc8d02db1b

This change is included in xserver 1.13.0, current RHEL6.4 build is xorg-x11-server-1.13.0-1.el6.


Comment 11 Ray Strode [halfline] 2012-12-14 19:36:03 UTC
*** Bug 848016 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2013-02-21 08:03:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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