Bug 603744

Summary: Unable to unlock screen
Product: [Fedora] Fedora Reporter: Akos Ladanyi <akos.ladanyi>
Component: gnome-screensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: brnpaolo, gerald, jmccann, rstrode, santtu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 18:12:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
gnome-screensaver log
glibc detected messages none

Description Akos Ladanyi 2010-06-14 13:28:31 UTC
Created attachment 423832 [details]
gnome-screensaver log

Description of problem:
After locking the screen it is not possible to unlock it. The unlock window with the password entry does not appear when touching the keyboard, just the gnome desktop background blinks in for a second, then the screen turns black again.

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

Steps to Reproduce:
1. Lock screen with 'System'->'Lock Screen'
2. Press any key
Actual results:
The unlock window does not appear.

Expected results:
The unlock window should appear.

Attached some logs.

Comment 1 Akos Ladanyi 2010-06-14 13:29:22 UTC
Created attachment 423834 [details]
glibc detected messages

Comment 2 Santtu Pajukanta 2010-06-18 07:27:38 UTC
On my box, this bug was fixed by some recent upgrade (xscreensaver-base
4.1.fc13.respin1 I guess).

I believe #597630 and #532901 are related.

Comment 3 Akos Ladanyi 2010-06-18 13:22:20 UTC
(In reply to comment #2)
> On my box, this bug was fixed by some recent upgrade (xscreensaver-base
> 4.1.fc13.respin1 I guess).
Yes, this seems to be resolved for me too.

Comment 4 Gerald Pfeifer 2010-06-20 16:15:39 UTC
Yes, this pretty much looks like a duplicate of the (earlier filed)
bug #597630 which has been resolved.

Comment 5 Bug Zapper 2011-06-02 10:55:21 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 6 Fedora Admin XMLRPC Client 2011-06-21 16:01:45 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Bug Zapper 2011-06-27 18:12:20 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.