Bug 349369 - Need to focus into password textbox after pressing alt+shift to change keyboard layout.
Summary: Need to focus into password textbox after pressing alt+shift to change keyboa...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-19 07:37 UTC by Mohammad Etemaddar
Modified: 2018-04-16 20:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mohammad Etemaddar 2015-06-19 07:37:54 UTC
I use two keyboard layouts: Persian and English. Sometimes when I have Persian layout selected and logout (or suspend, or lock), then, This layout is kept when I come back. I have to change to English using alt-shift. But after hitting alt+shift, It will be distracted focus from password textbox.
Then I can not go to password textbox using keyboard (Tab key)
I have to click On it.
I think it would be good to set focus into password textbox after changing keyboard layout.
I think it would be permit tab key to function at login time (in order to be able to login at similar situation)

Reproducible: Always

Steps to Reproduce:
1. add new keyboard layout to KDE.
2. select switch layout shortcut key to something like (alt+shift). I think it will be the same by default.
3. Change your keyboard layout to another layout (Optional).
4. logout from KDE, Or suspend, Or just lock the screen
4. Now you have to switch keyboard layout (using alt+shift) back to English in order to put password in English.

Actual Results:  
Focus will be distracted from password textbox.


my KDE version is 4.14.6 but I could not find it form the version list.
Comment 1 Nate Graham 2018-04-16 20:25:14 UTC
KDM is unmaintained and not used in KDE Plasma 5.

SDDM is the login manager used in KDE Plasma 5. If you still have this same issue with SDDM, please file an issue on the SDDM bugtracker (after doing a search for existing issues first!): https://github.com/sddm/sddm/issues/