Philip Müller

@entraide-net: accessibility is currently not our focus. It is still on our todo list, but with low priority. Currently we have to stabilize the install framework again.

Well, I've an update. **English** works. I entered `asdfg` instead of `asdfgh`, which was the password. So this leads to the issue with keyboard layouts in **grub** not in **English**...

Here is the [grub.cfg](https://pastebin.com/a0gz85Xu) file of the English installation. There I see a `set lang=en_US` ...

So in the end it is a keyboard layout issue by defaulting to US-EN on grub stage1. I found this [tutorial](https://superuser.com/questions/974833/change-the-keyboard-layout-of-grub-in-stage-1) on how to change it to DE-AT. Might work...

Similar topic was discussed in our [old forums](https://archived.forum.manjaro.org/t/change-keyboard-layout-in-grub-shell/155182).

[Here](https://itectec.com/ubuntu/ubuntu-how-to-change-grub-command-line-grub-shell-keyboard-layout/) is another one. Maybe we can implement some like this into **Calamares**.

Well, this might need to be the case when `/boot` is not encrypted, which brings us to this issue: https://github.com/calamares/calamares/issues/1311

On our end we enable it by default via our [tools](https://gitlab.manjaro.org/tools/development-tools/manjaro-tools/-/commit/b99d489ef500b336c210e21041e37eb07ceca2c7). It took me several patches to get this feature not having **os-prober** running by default [upstreamed](https://git.savannah.gnu.org/cgit/grub.git/commit/?id=54e0a1bbf1e9106901a557195bb35e5e20fb3925). The original patch...

See https://github.com/calamares/calamares/issues/1099

Sounds like special cases most of us don't use. However feel free @edmundlaugasson to do a PR for review ...