Bug 258548

Summary:	When screensaver is active, kcheckpass doesn't read the first key
Product:	[Unmaintained] kscreensaver	Reporter:	Jesús Guerrero Botella <jesus.guerrero.botella>
Component:	kcheckpass	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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.