Bug 243785

Summary: Typing at a screensaver should immediately activate the password field and pass the typed keys to it
Product: kscreensaver Reporter: Ryan Thompson <rct+bugs>
Component: generalAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description Ryan Thompson 2010-07-06 19:33:23 UTC
Version:           unspecified
OS:                Linux

If the screen is locked with Kscreensaver, one cannot simply type the password to unlock. One must type any random key or move the mouse in order to bring up the password dialog, and *then* type the password. Contrast xscreensaver, which passes all typing to the input field of the unlock dialog, so that one simply has to type one's password to unlock.

Reproducible: Always

Steps to Reproduce:
Assume that the password is "secret".

1. Lock the screen with Kscreensaver.
2. Make sure the unlock dialog is not shown yet.
3. Type the password "secret", and then press enter.

Actual Results:  
The password field clearly has 5 characters in it, which are of course "ecret". The "s" key that was pressed initially only activated the unlock dialog, but was not actually passed into the input field. Naturally, when enter is pressed, the screensaver will respond that the password was wrong.

Expected Results:  
The password field should receive all the characters that were typed, including the keypress that activated the dialog in the first place.

Contrast xscreensaver, which gets this right. I don't remember if gnome-screensaver gets this right or not.
Comment 1 Oswald Buddenhagen 2010-07-06 20:21:01 UTC
the definition of "right" is up for debate, anyway.

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