Bug 313587

Summary:	It's no longer possible to show unlocking password dialog by any key
Product:	[Unmaintained] kscreensaver	Reporter:	Jure Repinc <jlp>
Component:	locker-qml	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	minor	CC:	CisBug, mgraesslin, tunedconsulting
Priority:	NOR	Keywords:	regression
Version First Reported In:	4.9.98 RC3
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	xsession-error copy after locking the screen via "qdbus org.kde.ksmserver /ScreenSaver Lock"

Description Jure Repinc 2013-01-20 20:44:17 UTC

This is a regression from previous versions. When screen was locked I could immediately start entering the password and this showed the unlock password entry and it started accepting password I was entering. Now I always have to press Escape key before I can even start entering password.

Reproducible: Always

Steps to Reproduce:
1. wait until screen gets locked
2. start typing in your password
Actual Results:  
When you press a key for the first character of your password nothing happens, no screen unlock password entry dialog is shown and the pressed key doesn't get entered as the first character for password.

Expected Results:  
When you press any key on keyboard the unlock password entry dialog should be shown and if the pressed key represents a valid character for any password it should get entered a first character in unlock password entry dialog.

Comment 1 Rolf Eike Beer 2013-06-22 10:46:10 UTC

*** Bug 316602 has been marked as a duplicate of this bug. ***

Comment 2 Lorenzo 'tuned' 2014-03-11 20:32:51 UTC

Experienced the same really annoying issue:

1. Lock the screen normally with keyboard shortcut or desktop button. The unlock panel is there and works properly
2. The screen turn off after few minutes of inactivity
3. I turn back on the screen with any keyboard key or mouse movement and the unlock panel is not there anymore. No way to make it appear with Ctrl+Alt+L or Esc key.
4. Computer stucked and/or crashed and/or idle. Only way is to turn it off and reboot loosing all the session activity.

I will post my ~/.xsession-error below

Comment 3 Lorenzo 'tuned' 2014-03-11 20:36:12 UTC

Created attachment 85544 [details]
xsession-error copy after locking the screen via "qdbus org.kde.ksmserver /ScreenSaver Lock"

I'm running Opensuse 13.1 on x86_64 on a Tuxedo laptop

I lock the screen via "qdbus org.kde.ksmserver /ScreenSaver Lock" 
and before the unlock panel disappear I unlock in and get that errors

Comment 4 Lorenzo 'tuned' 2014-03-16 19:12:49 UTC

I solved this unselecting the auto locker from the screensaver properties window.
Now I just manually lock the screen, and the login panel is always available for unlocking, no more freezing or blocked screen

Comment 5 Martin Flöser 2015-01-26 07:54:45 UTC

The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.