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

R4.0-rc1 - Improper boot-time LUKS keyboard layout #2971

Closed
alexis- opened this Issue Aug 4, 2017 · 9 comments

Comments

Projects
None yet
5 participants
@alexis-

alexis- commented Aug 4, 2017

Qubes OS version (e.g., R3.2): R4.0-rc1

Affected TemplateVMs (e.g., fedora-23, if applicable): N/A


Expected behavior:

Keyboard layout during boot-time for LUKS disk encryption should be the one set by default, during the installation procedure.

Actual behavior:

Keyboard layout is set to qwerty, regardless of default keyboard layout.

Steps to reproduce the behavior:

  • Run Qubes R4.0-rc1 install
  • Select US language
  • Select a custom keyboard layout
  • Proceed with rest of configuration, and install (default options in my case)
  • At boot time, described issue occur

General notes:

Keyboard layout otherwise behaves as expected (after disk de-encryption)


Related issues:

@KuroSaru

This comment has been minimized.

Show comment
Hide comment
@KuroSaru

KuroSaru Aug 4, 2017

Can confirm this behaviour.

KuroSaru commented Aug 4, 2017

Can confirm this behaviour.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 4, 2017

Member

UEFI or legacy?

Member

marmarek commented Aug 4, 2017

UEFI or legacy?

@marmarek marmarek added this to the Release 4.0 milestone Aug 4, 2017

@alexis-

This comment has been minimized.

Show comment
Hide comment
@alexis-

alexis- Aug 4, 2017

UEFI here

alexis- commented Aug 4, 2017

UEFI here

@marmarek marmarek referenced this issue in QubesOS/qubes-doc Mar 19, 2018

Merged

consistent dracut commands across docs #599

@awokd

This comment has been minimized.

Show comment
Hide comment
@awokd

awokd Mar 19, 2018

Resolving #3624 might resolve this one too?

awokd commented Mar 19, 2018

Resolving #3624 might resolve this one too?

@alexis-

This comment has been minimized.

Show comment
Hide comment
@alexis-

alexis- Mar 23, 2018

I thought it was already solved ? I haven't faced this issue since RC2.

alexis- commented Mar 23, 2018

I thought it was already solved ? I haven't faced this issue since RC2.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 24, 2018

Member

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

Member

andrewdavidwong commented Mar 24, 2018

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

@awokd

This comment has been minimized.

Show comment
Hide comment

awokd commented Apr 1, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 1, 2018

Member

Is it the same as #3234? There were relevant fixes in final 4.0 that didn't managed to get into rc5.

Member

marmarek commented Apr 1, 2018

Is it the same as #3234? There were relevant fixes in final 4.0 that didn't managed to get into rc5.

@awokd

This comment has been minimized.

Show comment
Hide comment
@awokd

awokd Apr 1, 2018

Indeed; please disregard my comment!

awokd commented Apr 1, 2018

Indeed; please disregard my comment!

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