Bug 472184

Summary:	Unlock only possible after mouse click in password area when using 2 mirrorred screens
Product:	[Unmaintained] kscreenlocker	Reporter:	rik <rik>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate
Priority:	NOR	Keywords:	multiscreen
Version First Reported In:	5.27.7
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	6.0
Sentry Crash Report:
Attachments:	vid of the bug

Description rik 2023-07-12 10:24:16 UTC

Created attachment 160250 [details]
vid of the bug

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Hook up an additional screen to your laptop running Kubuntu 23.04 and set the laptop as primary and the 2nd screen as secondary and mirrored
2. Boot up and login to Kubuntu
3. Lock the screen with super-L
4. start typing as if you want to enter a password

OBSERVED RESULT
nothing happens, the password field does not even become visible

EXPECTED RESULT
the password field becomes visible and the password gets typed in the password field

5. now move the mouse 

OBSERVED RESULT
now the password field becomes visible, but the password still does not get typed in the password field

6. now left-click the mouse in the password field

OBSERVED RESULT
Only now does the password get typed in the password field

--> see attached vid

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 23.04, KDE 5.27
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 rik 2023-07-12 10:25:07 UTC

PS I remember this same bug occurring on 22.04 or 22.10 when i tried that on a previous laptop. 
This is on a Lenovo T15 gen2. 
Previous laptop was an HP.

Comment 2 Nate Graham 2023-09-12 20:23:23 UTC

With that exact screen setup in Plasma 6 Wayland, I can't reproduce the bug. So let's assume for now that it's fixed!