-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Keyboard layout does not persist in installer #3352
Comments
It is a duplicated of #3234 |
This issue may be related to #3234, but it is certainly not a duplicate. This issue is about the keyboard layout switching back to US when a user is created in the installer, which means the user password is set with the wrong keyboard layout, while #3234 speaks about the password for disk encryption being set with the wrong keyboard layout. I did not have a problem with the disk encryption password (if I had, I would never have discovered that I had a problem with the user password). |
I see your point. I misread your issue. |
@ohreally so, for disk passphrase prompt (both in installer, and later on system start), the layout is correctly set to FR? Or it is just the same and you don't really know which one? |
I'm not entirely sure which one.
So I'd say my disk encryption password was (correctly) set using the French layout, while my user password was (incorrectly) set using the US layout. |
I can confirm this, and have a test case here: https://openqa.qubes-os.org/tests/529 |
Copying @Aekez comment #4013 (comment):
|
I can confirm that during installation (at least) So, at least we can trigger the problem without going through full installation each time. |
According to strace, the only thing that touches Xorg is udev, and it doesn't send anything about keyboard layout. So it isn't anything else processing udev events and re-configuring X server. It's X server itself. BTW |
Looks similar to this Xorg bug: https://bugs.freedesktop.org/show_bug.cgi?id=71168 |
Further finding from analyzing Xorg source code:
So, it looks like the only way to change default layout at runtime, is to add new keyboard with desired
And indeed, adding an udev rule that set |
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Xorg loads keyboard layout for new devices (or existing one re-detected) only from its config, ignoring runtime changes done in the meantime (setxkbmap etc). Since installation process calls udevadm trigger somewhere, all input devices are re-discovered and reverted to default keyboard layout (us). Avoid this by configuring current keyboard layout also as udev rules, which are loaded by Xorg while discovering device. Fixes QubesOS/qubes-issues#3352
Qubes OS version:
R4.0-rc3
Affected TemplateVMs:
N/A
Steps to reproduce the behavior:
Start the installer. Set the keyboard layout to French. Do or do not delete the original (US) layout; this does not make a difference.
Expected behavior:
Keyboard layout is and stays French.
Actual behavior:
When creating a user account (in the installer), the keyboard layout changes back to the original (US) layout, with no way of correcting this. This results in the password being set using the US layout. However, after reboot, on login, the keyboard layout is back to FR, which makes it extremely difficult to guess one's own password.
The text was updated successfully, but these errors were encountered: