systemd-248~rc2-1.fc34.x86_64 systemd-udev-248~rc2-1.fc34.x86_64 [alessio@fedora ~]$ systemctl status systemd-vconsole-setup.service × systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) Active: failed (Result: exit-code) since Mon 2021-03-01 23:11:21 CET; 3min 36s ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Process: 547 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=1/FAILURE) Main PID: 547 (code=exited, status=1/FAILURE) CPU: 49ms Mar 01 23:11:21 fedora systemd-vconsole-setup[558]: loadkeys: Unable to open file: it2: No such file or directory Mar 01 23:11:21 fedora systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Mar 01 23:11:21 fedora systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. Mar 01 23:11:21 fedora systemd[1]: Failed to start Setup Virtual Console.
This could be a possible duplicate of BZ#1852427
Using KEYMAP="it" instead of "it2" in /etc/vconsole.conf, then the service start successfully.
The service start successfully, it seems if using systemctl status systemd-vconsole-setup.service once logged in. But during the boot process some [FAILED] lines appear.
Created attachment 1760108 [details] failed during early boot process
Created attachment 1760109 [details] failed during boot process
Oh, ok. Regenerating also dracut sudo dracut --force also the [FAILED] lines during the boot are gone.
it2 is in kbd-legacy, and previously kbd-legacy was pulled in by kbd. This dependency was dropped fairly recently in kbd-2.3.0-4. But this doesn't explain why you got the error, i.e. what put "it2" in /etc/vconsole.conf. Was this on a newly installed system? Because on an upgraded system, if you had kbd-legacy, you should still have it after an upgrade.
rpm -qa|grep '^kbd' ?
(In reply to Zbigniew Jędrzejewski-Szmek from comment #8) > rpm -qa|grep '^kbd' ? $ rpm -qa|grep '^kbd' kbd-misc-2.4.0-2.fc34.noarch kbd-2.4.0-2.fc34.x86_64
(In reply to Zbigniew Jędrzejewski-Szmek from comment #7) > Was this on a newly installed system? Because on an upgraded system, if you Newly installed F34 system.
Oh, OK. So something is configuring "it2" without pulling in -legacy. Maybe it's Anaconda as mentioned in #1852427. But I see that localed accepts any invalid keymap without any complaint, even though it doesn't have the specified keymap in 'list-keymaps'. I think we should refuse.
*** Bug 1852427 has been marked as a duplicate of this bug. ***
https://github.com/systemd/systemd/pull/18875 @adamw: if this goes in, localed will flat out refuse to set a non-installed keymap. This should be OK in general. Anaconda might be surprised by the error though. So we need to make sure that this is handled gracefully in the installer.
FEDORA-2021-ea92e5703f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea92e5703f
FEDORA-2021-ea92e5703f has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ea92e5703f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea92e5703f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-ea92e5703f has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Bug still present in RHEL 9.1
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days