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 594696 - Dock / Undock and sleep/wake - unable to unlock screen
Summary: Dock / Undock and sleep/wake - unable to unlock screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-screensaver
Version: 6.0
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: jmccann
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
: 577181 583661 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-21 11:19 UTC by Chris Ward
Modified: 2015-01-14 23:25 UTC (History)
6 users (show)

Fixed In Version: gnome-screensaver-2.28.3-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 20:31:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 619773 0 None None None Never

Description Chris Ward 2010-05-21 11:19:25 UTC
Description of problem:


Version-Release number of selected component (if applicable):
Latest packages as of 
http://download.englab.brq.redhat.com/pub/rhel/rel-eng/RHEL6.0-20100512.0/6.0/Server/x86_64/os/


Steps to Reproduce:
example 1
1. Boot laptop undocked
2. login
3. sleep
4. dock
5. wake

example 2
1. Boot laptop docked
2. login to gnome
3. switch off laptop monitor, leaving external display ON
4. Close laptop screen
5. Set preferences so when no power and laptop screen is closed system will sleep
6. Undock system (system will sleep)
7. Dock system (while sleeping
8. Wake system (open laptop)

  
Actual results:
System wakes and screen-saver lock dialogue pops up but user is unable to input.
User must wait until the screen lock time-out occurs. Then when the dialogue pops up again, user is able to input.

Expected results:
user should be able to input without having to wait for the timeout

Additional info:

Comment 1 RHEL Program Management 2010-05-21 11:35:45 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Chris Ward 2010-05-25 08:55:38 UTC
I just reproduced this again also using the following steps. 

1. boot system docked. 
2. Log-in
3. sleep system
4. Undock system
5. Wake system
6. Sleep system
7. Dock system
5. wake system
6. once screen-saver prompts for password, dock system

Comment 3 Chris Ward 2010-05-25 08:57:09 UTC
Arg. Sorry. Ignore comment #2.. (i'm slow today)

1. boot system docked. 
2. Log-in
3. sleep system
4. Undock system
5. Wake system
6. Sleep system
7. Dock system
8. wake system
9. once screen-saver prompts for password, notice how screensaver lock doesn't respond to keyboard / mouse input.

Comment 5 Chris Ward 2010-05-27 07:18:23 UTC
Thanks for the work on solving this William!!!

Comment 6 jmccann 2010-05-27 14:13:48 UTC
*** Bug 583661 has been marked as a duplicate of this bug. ***

Comment 7 jmccann 2010-06-04 19:26:33 UTC
*** Bug 577181 has been marked as a duplicate of this bug. ***

Comment 9 Michal Haško 2010-07-01 08:25:33 UTC
I am working on this to verify it.

Comment 10 Michal Haško 2010-07-02 14:17:40 UTC
VERIFIED

I was able to successfully unlock screen in all the scenarios below

    +----------+--------+---------+
    |          | LOCK & | SLEEP & |
    |          | RESUME | WAKE UP |
    +----------+--------+---------+
    |  DOCKED  |   ok   |    ok   |
    +----------+--------+---------+
    | UNDOCKED |   ok   |    ok   |
    +----------+--------+---------+

                               ACTIONS
    +----------+------------------+----------------+
    |          |   SLEEP DOCKED   | SLEEP UNDOCKED |
    |          | WAKE UP UNDOCKED | WAKE UP DOCKED |
    +----------+------------------+----------------+
D S | MIRRORED |        ok        |       ok       |
I E +----------+------------------+----------------+
S T | EXTENDED |        ok        |       ok       |
P T +----------+------------------+----------------+
L I | INTERNAL |        ok        |       ok       |
A N +----------+------------------+----------------+
Y G | EXTERNAL |        ok        |       ok       |
  S +----------+------------------+----------------+

Comment 11 releng-rhel@redhat.com 2010-11-10 20:31:50 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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