Bug 1014801

Summary: System keyboard layout set to Norwegian leads to Dvorak layout on LUKS passphrase screen
Product: [openSUSE] openSUSE Tumbleweed Reporter: Forgotten User DbAFyTVGEb <forgotten_DbAFyTVGEb>
Component: BasesystemAssignee: Stanislav Brabec <sbrabec>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: anicka, mmachova, mmarek, sbrabec, zaitor
Version: Current   
Target Milestone: ---   
Hardware: All   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 1012230    
Bug Blocks:    

Description Forgotten User DbAFyTVGEb 2016-12-09 11:05:11 UTC
It seems that setting the system keyboard layout to Norwegian leads to Dvorak layout being selected on the LUKS passhprase screen during boot. This happens both when selecting Norwegian keyboard layout on a fresh install and when selecting Norwegian as system keyboard layout through YaST.

I recieved a tip on IRC from a helpful user that the problem is likely connected to kbd-legacy containing two different no.map.gz files. One in the dvorak folder and one in the qwerty folder.

To reproduce:
* Have a system that requires a LUKS passphrase on boot.
* Set system keyboard layout to Norwegian.
* Attempt to enter passphrase with keys as on a QWERTY Norwegian layout (almost the same as most other 105-key layouts).
* Actually log in by typing using a Dvorak layout.
Comment 1 Bjørn Lie 2016-12-09 11:12:03 UTC
Adding bugowner of kbd to cc.

imho we should probably just nuke all of norwegian layouts from the legacy package, they serve no purpose anymore.
What we have in "new" kdb is far superior.
Comment 2 Bjørn Lie 2016-12-09 11:14:42 UTC
Adding co-maintainers as well.
Comment 3 Stanislav Brabec 2016-12-13 19:43:09 UTC
Yes, it is possible that it picks bad keymap (or exactly not bad, just unexpected).

kbd changed its directory layout. We either need to define expected search path, or always use qwerty/no etc.

Probably related with bug 1012230.
Comment 4 Markéta Machová 2020-05-26 15:09:27 UTC
Tha kbd-legacy has been cleaned up (and deleted) in the meantime. So this is probably fixed.