http://bugzilla.opensuse.org/show_bug.cgi?id=1103670 http://bugzilla.opensuse.org/show_bug.cgi?id=1103670#c1 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |massimo.burcheri@gmx.de Flags| |needinfo?(massimo.burcheri@ | |gmx.de) --- Comment #1 from Michael Chang --- (In reply to Massimo Burcheri from comment #0)

New installation of LEAP 15.0 with full encryption including /boot does prompt for the grub cryptodisk password but does not respect the DE keymap selected at installation, whereas following password prompts for /etc/crypttab volumes does respect the DE keymap.

Do you use any non ascii character for password ?

In combination one need to type "different" passwords for both prompts regarding the different keymaps.

Would you mind to provide an example to help understanding the problem ? Please note that grub2 input does not support dead key like circumflex. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103670 http://bugzilla.opensuse.org/show_bug.cgi?id=1103670#c3 --- Comment #3 from Massimo Burcheri --- The password contains a '-' character which is on different keycode for the US and the german DE layout. (In reply to Michael Chang from comment #2)

zypper in console-setup zypper in xkbcomp grub2-kbdcomp -o /boot/grub2/de.gkb de

# grub2-kbdcomp -o /boot/grub2.de.gkb de WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" WARNING: Unknown X keysym "dead_belowmacron" Unknown keyboard scan identifier KP_Comma Unknown keyboard scan identifier KP_Comma Unknown keyboard scan identifier KP_Comma Unknown keyboard scan identifier KP_Comma Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f Sorry, I can't test this anymore as I changed my LEAP installation to separate /boot partition and /etc/crypttab only for the luksOpen. There the keymap is correct. Would you agree that the LEAP installation should set and install the right grub keymap for grub cryptodisk? Or is this only a rare case on special firmware and default console input? Using the wrong keymap is hard to detect when using a sophisticated password at installation and it's just failing at reboot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103670 http://bugzilla.opensuse.org/show_bug.cgi?id=1103670#c5 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michael Chang --- To change the keymap, currently it requires to take manual step outlined in comment#2 and use own keyboard driver like at_keyboard to read scancode and map to keycode. Currently the configuration only support using firmware console input which read out keycode directly thus offer no custom keymap change capability. I still think we better stay with the default to be firmware console since it works more robust. We can automate the manual step via providing change keymap function in YaST, but that better be driven by Feature (FATE) not bug fixing here, -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103670 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |FEATURE -- You are receiving this mail because: You are on the CC list for the bug.