Bug 501873

Summary:	Timeout on unlocking screen after suspend
Product:	[Fedora] Fedora	Reporter:	Jan Drábek <repli2dev>
Component:	gnome-screensaver	Assignee:	jmccann
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	cschalle, james, jmccann, mschmidt, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-31 10:46:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Drábek 2009-05-21 07:55:16 UTC

Description of problem:
After waking up laptop I get unlocking dialog but I cannot type password, there is only "Timeout". Then screen goes black and I have to wait about ten seconds.

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

How reproducible:
always

Steps to Reproduce:
1. Log on
2. Suspend laptop
3. Wake it
  
Actual results:
Have to wait before unlocking.

Expected results:
I should be able to type password immediately.

Additional info:
If I press CTRL+ALT+F2 in time of "Timeout" gdm restart itself. Is that bug or feature?

Comment 1 Michal Schmidt 2009-05-31 10:46:20 UTC

(In reply to comment #0)
> Description of problem:
> After waking up laptop I get unlocking dialog but I cannot type password,
> there is only "Timeout".

I can reproduce this.

> Then screen goes black and I have to wait about ten seconds.

Why the ten seconds? For me the timeout message lasts for about 3 seconds and then I can press a key to get a new unlocking dialog immediately.

> Version-Release number of selected component (if applicable):
> Gnome 2.26.1
> 
> How reproducible:
> always
> 
> Steps to Reproduce:
> 1. Log on
> 2. Suspend laptop

... and leave it suspended for at least a minute (the length of the password entry timeout).

> 3. Wake it
> 
> Actual results:
> Have to wait before unlocking.
> 
> Expected results:
> I should be able to type password immediately.
> 
> Additional info:
> If I press CTRL+ALT+F2 in time of "Timeout" gdm restart itself. Is that bug or
> feature?  

I can't reproduce this one and it looks like an unrelated issue. Probably your X server crashes. Examine your X log and file another bug.


The password timeout after suspend was already reported as bug 497655.

*** This bug has been marked as a duplicate of bug 497655 ***