I can confirm this bug. But a qemu machine seems unaffected.
There is another effect: Step 1: Let the GRUB console start. Step 2: select console as terminal_input and terminal_output. This is the default anyways. Step 3: set a non-US keyboard layout since console is the active terminal_input, the new layout has no effect yet Step 4: set console AND at_keyboard (both! This is possible) as terminal_input now ALL keys you press are handled by at_keyboard. You can detect this because the non-US keyboard layout is used for all keys pressed. There is no delay, everything just works great right now. Step 5: activate gfxterm as terminal_output Now strange things happen: press a key that would be affected by the non-US keboard layout. You get random output now: the character you see can be affected by the non-US layout, it can be the US layout character or the keypress does nothing at all. The only difference to step 4: gfxterm is active Why does gfxterm affect at_keyboard? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914953 Title: grub2 incompatibility between at_keyboard and gfxterm modules lead to impossible to type passphrase or access ubuntu grub2 menu on a fully encrypted installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1914953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
