Bug 331783

Summary:	screenlocker password field loosing focus after keyboard layout switch
Product:	[Plasma] plasma4	Reporter:	intruderkw
Component:	screensaver overlay	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	chanika, nplatis
Priority:	NOR
Version:	4.12.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description intruderkw 2014-03-05 21:18:00 UTC

keyboard layout is set in xserver, greeting dialog appears after boot or wake up from standby/hibernate, the focus is on the password field. I do a layout switch shortcut(alt-shift) and the focus is off, no way to get it back by keyboard(tab, ctrl-tab, alt-tab etc.), the only way is to use the mouse.

Reproducible: Always

Steps to Reproduce:
1. you should have at least two kb layouts setted in Xconfig und a shortcut switch for
2. boot or wake up from standby/hibernate
3. du a shortcut to switch the layout
Actual Results:  
the focus is off from pwd field

Expected Results:  
the focus remains in the pwd field

actually kde 4.12.1

Comment 1 Christoph Feck 2014-03-16 13:27:05 UTC

Are you sure this is kdm and not the screen locker dialog?

Comment 2 intruderkw 2014-03-17 11:03:39 UTC

hmm, so if kdm have in general nothing to to with screenlocking, then this bug belongs somewhere else. Plasma perhaps?

Comment 3 intruderkw 2014-03-17 11:17:37 UTC

I need to correct this one, it concerns just screensaver alone, no kdm. So my description is somewhat inaccurate, the normal boot process and kdm greeting are not affected. 


@Christoph Feck
 Thank You

Comment 4 Nikos Platis 2014-10-13 07:26:51 UTC

Confirming this bug on KDE 4.14.1.

Comment 5 Nate Graham 2018-06-08 18:37:03 UTC

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham