Description of problem:
After boot the vconsole keymap was not loaded (In DE swapped y and z are pretty obvious) and an error message appeared on the vconsole.
Version-Release number of selected component (if applicable):
systemd-udev-255.4-1-fc40.x86_64
How reproducible:
Perform a dnf system-upgrade from Fedora 39 to 40 on a virtual machine I've been upgrading for more than a decade now. The virtual machine boots to a virtual console based login rather than a graphical one.
Steps to Reproduce:
1. dnf system-upgrade download --releasever=40
2. dnf system-upgrade reboot
3. Wait for upgrade and subsequent reboot to complete
Actual results:
After a fresh boot the virtual console shows an error message:
systemd[1]: Failed to start systemd-vconsole-setup.service - Virtual Console Set
The keymap was not loaded.
Expected results:
No error message before login prompt on virtual console
Keymap loads
Additional info:
❯ sudo systemctl status systemd-vconsole-setup.service
× systemd-vconsole-setup.service - Virtual Console Setup
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Wed 2024-04-03 20:49:53 CEST; 1h 58min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Main PID: 650 (code=exited, status=1/FAILURE)
CPU: 8ms
Apr 03 20:49:53 HOSTNAME systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
Apr 03 20:49:53 HOSTNAME systemd-vconsole-setup[650]: Failed to lock /dev/console: Input/output error
Apr 03 20:49:53 HOSTNAME systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE
Apr 03 20:49:53 HOSTNAME systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
Apr 03 20:49:53 HOSTNAME systemd[1]: Failed to start systemd-vconsole-setup.service - Virtual Console Setup.
❯ cat /etc/vconsole.conf
FONT=latarcyrheb-sun16
KEYMAP=de-latin1-nodeadkeys
Google found this bug when searching for "Failed to lock /dev/console", so upstream should be aware of the problem, no reaction since mid december though: https://github.com/systemd/systemd/issues/30501
I found a solution for my personal problem that I wanted to share with you in the upstream ticket: https://github.com/systemd/systemd/issues/30501
I personally don't need this bug ticket anymore, feel free to close it or keep it around until a proper fix has been implemented.
Comment 2Zbigniew Jędrzejewski-Szmek
2024-05-14 18:12:30 UTC
Comment 4Fedora Update System
2024-05-15 15:47:18 UTC
FEDORA-2024-0920709321 (systemd-256~rc2-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.
Description of problem: After boot the vconsole keymap was not loaded (In DE swapped y and z are pretty obvious) and an error message appeared on the vconsole. Version-Release number of selected component (if applicable): systemd-udev-255.4-1-fc40.x86_64 How reproducible: Perform a dnf system-upgrade from Fedora 39 to 40 on a virtual machine I've been upgrading for more than a decade now. The virtual machine boots to a virtual console based login rather than a graphical one. Steps to Reproduce: 1. dnf system-upgrade download --releasever=40 2. dnf system-upgrade reboot 3. Wait for upgrade and subsequent reboot to complete Actual results: After a fresh boot the virtual console shows an error message: systemd[1]: Failed to start systemd-vconsole-setup.service - Virtual Console Set The keymap was not loaded. Expected results: No error message before login prompt on virtual console Keymap loads Additional info: ❯ sudo systemctl status systemd-vconsole-setup.service × systemd-vconsole-setup.service - Virtual Console Setup Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Wed 2024-04-03 20:49:53 CEST; 1h 58min ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Main PID: 650 (code=exited, status=1/FAILURE) CPU: 8ms Apr 03 20:49:53 HOSTNAME systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup... Apr 03 20:49:53 HOSTNAME systemd-vconsole-setup[650]: Failed to lock /dev/console: Input/output error Apr 03 20:49:53 HOSTNAME systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Apr 03 20:49:53 HOSTNAME systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. Apr 03 20:49:53 HOSTNAME systemd[1]: Failed to start systemd-vconsole-setup.service - Virtual Console Setup. ❯ cat /etc/vconsole.conf FONT=latarcyrheb-sun16 KEYMAP=de-latin1-nodeadkeys Google found this bug when searching for "Failed to lock /dev/console", so upstream should be aware of the problem, no reaction since mid december though: https://github.com/systemd/systemd/issues/30501