New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphical Installer: Wrong keyboard layout for Grub / LUKS #3748

Closed
diffusae opened this Issue Mar 26, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@diffusae

Qubes OS version:

R4.0rc5

Affected component(s):

Graphical Installer


Steps to reproduce the behavior:

If you use the graphical installer and change the keyboard layout (and not the system language).
The keyboard layout for LUKS passphrase will be set correctly, but nevertheless Grub uses the default keyboard layout after booting.

Expected behavior:

Should set the correct keyboard layout for Grub.

Actual behavior:

You could change the layout, but for the Grub installation it remains to US.

General notes:

It should be possible to change this afterwards.


Related issues:

?

@diffusae diffusae changed the title from Wrong keyboard layout for grub / LUKS to Wrong keyboard layout for Grub / LUKS Mar 26, 2018

@diffusae diffusae changed the title from Wrong keyboard layout for Grub / LUKS to Graphical Installer: Wrong keyboard layout for Grub / LUKS Mar 26, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 27, 2018

Member

Duplicate of #3234

Member

andrewdavidwong commented Mar 27, 2018

Duplicate of #3234

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3234 Mar 27, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 27, 2018

Member

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Mar 27, 2018

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment