Bug 72390 - First keypress is ignored on locked screen
Summary: First keypress is ignored on locked screen
Keywords:
Status: CLOSED DUPLICATE of bug 69039
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xscreensaver
Version: null
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-23 13:43 UTC by Steve Fox
Modified: 2014-03-17 02:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-23 13:43:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Fox 2002-08-23 13:43:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
gtk lock screen doesn't record first key press as a password character.

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


How reproducible:
Always

Steps to Reproduce:
With the non-gtk lock screen, you could begin typing your password to initiate
the password dialog. With the gtk lock screen (with locks very nice with the
exception of jwz's ugly flame), you have to press a key first to initiate the
password dialog. People used to the old lock screen will keep typing their
password and having it fail, not realizing that the first character is not being
sent to the dialog, but rather to initiate the dialog. Unless there is a reason
for this new behavior, I would prefer the old behavior. Thanks.

Additional info:

Comment 1 Bill Nottingham 2002-08-23 20:51:12 UTC

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


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