Bug 1629350
| Summary: | Keymap doesn’t get set correctly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frank <frank.bruetting> |
| Component: | dracut | Assignee: | dracut-maint-list |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | dracut-maint-list, elad, fedora, guillaume-redhat, hdegoede, jonathan, rstrode, zbyszek |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dracut-050-61.git20200529.fc31 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-18 15:47:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Any progress on this? It’s very annoying to always enter passwords in a total different keyboard layout. And this is reproducible on other machines. :/ This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reproducible with FSB30. plymouth does not set the keymap itself, it simply uses the keymap as setup by the initrd environment. The initrd is generated by dracut and should inherit the settings from vconsole.conf, see: /usr/lib/dracut/modules.d/00systemd/module-setup.sh Note it only does this when building a host-only initrd (the default) have you perhaps changed the dracut config? What is the output of: "sudo lsinitrd | grep vconsole" ? This should include etc/vconsole.conf if not you've likely set the dracut hostonly option to no/false. Changing component to dracut. Yes, in the meantime I was told the same in Fedora-Discourse: https://discussion.fedoraproject.org/t/bug-dm-crypt-password-saved-in-qwerty/1204/8 ``` sudo lsinitrd | grep vconsole No <initramfs file> specified and the default image '/boot/initramfs-5.1.18-300.fc30.x86_64.img' cannot be accessed! ``` This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Still occurring in FSB31 (maybe Silverblue-specific). FEDORA-2020-03e14f6120 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-03e14f6120 FEDORA-2020-03e14f6120 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-03e14f6120` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-03e14f6120 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Is there an equivalent to do this in Silverblue? Ah sorry, it's mentioned there. FEDORA-2020-03e14f6120 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. Hi, I've tested Silverblue in march 2019 and had this bug too. The experience was too bad for me, back to Fedora Workstation, and today I'm trying again Silverblue Beta. This bug is still here. Also, in Workstation, the layout is show in dracut, but not in Silverblue. |
Description of problem: On both F28 and F29, I set my systems up with keymaps "de-neo" (primary) and "de-nodeadkeys" (secondary). Anaconda also states, that the primary keymap will be used at boot – but since F28 this doesn’t work anymore. I instead always have to type in my password via a US keymap. With help of Christian Schaller, I was able to find out that `localectl`, the keymap in the initrd and `/etc/vconsole.conf` all were set up properly. I had to manually add "vconsole.keymap=de-neo" in the kernel command line for the layout to be correct. So it seams that plymouth isn’t correctly configured and/or not able to read `/etc/vconsole` correctly. Version-Release number of selected component (if applicable): Since plymouth of F28 How reproducible: Every time Steps to Reproduce: 1. Chose Neo as primary keympa in Anaconda. 2. Set encrypted drive. 3. Plymouth keymap will be US Additional info: $ localectl System Locale: LANG=de_DE.UTF-8 VC Keymap: de-neo X11 Layout: de,de X11 Variant: neo,nodeadkeys $ cat /etc/vconsole.conf KEYMAP="de-neo" FONT="eurlatgr"