Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Keyboard layout choosen during install is not correctly configured after install when running Qubes-OS 4.1 Beta 1 #6860

Closed
stman opened this issue Aug 26, 2021 · 6 comments
Closed

Keyboard layout choosen during install is not correctly configured after install when running Qubes-OS 4.1 Beta 1 #6860

stman opened this issue Aug 26, 2021 · 6 comments
Labels
C: installer localization This issue concerns translating things into different languages or adapting them to other regions. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@stman
Copy link

stman commented Aug 26, 2021 •
edited
Loading

Qubes-OS 4.1 Beta 1

Issue details

When installing Qubes-OS 4.1 Beta and choosing a specific keyboard layout during the installation process, this setting is not fully configured later on in Qubes-OS when running Qubes-OS :

It's okay for dom0, but not for all other VM's, where the default english layout will apply.

To correct this, one needs to manualy uncheck the [Dom0] Keyboard utility’s “Use system defaults” box from the Layout tab to force the choosen keyboard layout during installation process to be applied to all VM’s.

If not doing so, the choosen configuration for the keyboard layout choosen during install won’t be applied to all VM’s.

This small configuration bug was not present on the 4.0.4 release of Qubes-OS

Steps to reproduce

See above. It's straight easy.

Expected behavior

The “Use system defaults” should be unchecked automatically after installation process, like it was the case in Qubes-OS 4.0.4

Actual behavior

Dom0 uses the choosen keyboard layout during the installation process (Can be easily checked by launching dom0's terminal), but within all other VM's, it's the english layout that is by default activated.
@stman stman added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug labels Aug 26, 2021
@andrewdavidwong andrewdavidwong added C: installer needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. localization This issue concerns translating things into different languages or adapting them to other regions. labels Aug 26, 2021
@andrewdavidwong andrewdavidwong added this to the Release 4.1 milestone Aug 26, 2021
@andrewdavidwong
Copy link
Member

@marmarek:

Assigned to the 4.1 milestone as this appears to be partially diagnosed and sounds like it should be relatively easy to fix in time. Please feel free to move it.

Also, I searched for duplicates, but the issues I found seemed to be at least slightly different. Apologies if I missed a duplicate.

@stman
Copy link
Author

stman commented Aug 27, 2021 •
edited
Loading

Hello Andrew.

The diagnosis was confirmed by BigQ on Qubes Community forums :

https://forum.qubes-os.org/t/4-1-beta-keyboard-layout-choosen-during-install-not-applied-correctly-once-installed/5933

It's a very simple installation auto configuration bug that should be fixed in a snap.

Shall I provide something else here to confirm the diagnosis ? Like some logs or whatever ?

@stman stman changed the title Keyboard layout choosen during install is not correctly configured after install when running Qubes-OS Keyboard layout choosen during install is not correctly configured after install when running Qubes-OS 4.1 Beta 1 Aug 27, 2021
@unman
Copy link
Member

unman commented Aug 27, 2021 via email

@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. 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.

@andrewdavidwong andrewdavidwong added R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Aug 27, 2021
@stman
Copy link
Author

stman commented Aug 28, 2021

Yes it is a duplicate, you are right. Still there is more info in my description as I give a workaround. Shall I copy/past my text in this duplicate then ?

@andrewdavidwong
Copy link
Member

Yes it is a duplicate, you are right. Still there is more info in my description as I give a workaround. Shall I copy/past my text in this duplicate then ?

Yes, please feel free to copy any pertinent information as a comment onto #6814 (if it's missing from that issue).

@andrewdavidwong andrewdavidwong removed this from the Release 4.1 milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: installer localization This issue concerns translating things into different languages or adapting them to other regions. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stman @andrewdavidwong @unman