Bug 258548 - When screensaver is active, kcheckpass doesn't read the first key
Summary: When screensaver is active, kcheckpass doesn't read the first key
Status: RESOLVED DUPLICATE of bug 37838
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: kcheckpass (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 11:24 UTC by Jesús Guerrero Botella
Modified: 2010-12-02 11:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jesús Guerrero Botella 2010-12-02 11:24:48 UTC 
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

When the screensaver is active, the first key you press is not read. Instead it "awakes" the password dialog, then you can type the password.

This is different from other screensavers. In xscreensaver -for example- I just start typing my password directly, and by the time I finish doing so my monitor is on again and my desktop is unlocked. xlockmore works mostly the same way, without even bringing up a dialog. Both cases, I don't have to press one key, wait for the dialog to come up and then write the password. I find that a bit obstructive.

It would be nice if an option could be added to let me write my password directly, without having to press any random key before that. I really don't care if the dialog appears or not.

Reproducible: Didn't try
Comment 1 Oswald Buddenhagen 2010-12-02 11:31:15 UTC 

*** This bug has been marked as a duplicate of bug 37838 ***
Comment 2 Jesús Guerrero Botella 2010-12-02 11:36:04 UTC 
Thanks. I tried to search but I wasn't able to find the right words, it seems. Case closed.