Bug 1217971 - [Build 44.1] systemd-vconsole-setup error "KD_FONT_OP_GET failed"
Summary: [Build 44.1] systemd-vconsole-setup error "KD_FONT_OP_GET failed"
Status: RESOLVED DUPLICATE of bug 1215282
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP6
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: Other Other
: P2 - High : Normal
Target Milestone: ---
Assignee: systemd maintainers
QA Contact:
URL: https://openqa.suse.de/tests/13005489...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-12 08:01 UTC by Timo Jyrinki
Modified: 2023-12-28 13:49 UTC (History)
7 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments
journal log (275.64 KB, text/x-log)
2023-12-12 08:01 UTC, Timo Jyrinki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timo Jyrinki 2023-12-12 08:01:29 UTC
Created attachment 871281 [details]
journal log

openQA test in scenario sle-15-SP6-Online-aarch64-apparmor_profile@aarch64 fails in
[consoletest_setup](https://openqa.suse.de/tests/13005489/modules/consoletest_setup/steps/71)

Last good: See Build 40.1, run 18 days ago at: https://openqa.suse.de/tests/12895042#step/consoletest_setup/68

The journal has additionally:
Dec 08 12:14:57.439385 localhost systemd-vconsole-setup[370]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
Dec 08 12:14:57.439417 localhost systemd-vconsole-setup[370]: Fonts will not be copied to remaining consoles
Comment 3 Antonio Feijoo 2023-12-13 11:31:56 UTC
As a coincidence, I also saw this error message on my Fedora 40 vm while testing systemd-v255:

> root@fedora:/home/dev# systemctl --version
> systemd 255 (255-1.fc40)
> +PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified
> root@fedora:/home/dev# journalctl -b | grep -e "Switching root" -e systemd-vconsole-setup
> Dec 13 09:30:27 fedora systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
> Dec 13 09:30:27 fedora systemd-vconsole-setup[278]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
> Dec 13 09:30:27 fedora systemd-vconsole-setup[281]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
> Dec 13 09:30:27 fedora systemd-vconsole-setup[278]: Setting source virtual console failed, ignoring remaining ones.
> Dec 13 09:30:27 fedora systemd[1]: Finished systemd-vconsole-setup.service - Virtual Console Setup.
> Dec 13 09:30:27 fedora systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
> Dec 13 09:30:27 fedora systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
> Dec 13 09:30:27 fedora systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup...
> Dec 13 09:30:27 fedora systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
> Dec 13 09:30:27 fedora systemd-vconsole-setup[477]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
> Dec 13 09:30:27 fedora systemd-vconsole-setup[459]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
> Dec 13 09:30:27 fedora systemd-vconsole-setup[459]: Setting source virtual console failed, ignoring remaining ones.
> Dec 13 09:30:27 fedora systemd[1]: Finished systemd-vconsole-setup.service - Virtual Console Setup.
> Dec 13 09:30:28 fedora systemd[1]: Switching root.
> Dec 13 09:30:29 fedora systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
> Dec 13 09:30:29 fedora systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
> Dec 13 09:30:29 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Dec 13 09:30:29 fedora systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup...
> Dec 13 09:30:29 fedora systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
> Dec 13 09:30:29 fedora systemd-vconsole-setup[734]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
> Dec 13 09:30:29 fedora systemd-vconsole-setup[734]: Fonts will not be copied to remaining consoles
> Dec 13 09:30:29 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Dec 13 09:30:29 fedora systemd[1]: Finished systemd-vconsole-setup.service - Virtual Console Setup.
Comment 5 Franck Bui 2023-12-13 12:44:14 UTC
Yes it's a duplicate of bsc#1215282 although it seems that the issue is happening  on a non live image in this case.

Reason is that tty1 is left in "graphics" mode and systemd-vconsole-setup doesn't handle this case very well.

I'm still trying to find out why tty1 is in graphics mode. That's normally shouldn't happen.
Comment 6 Franck Bui 2023-12-13 12:45:11 UTC
Is this issue also happening x86_64 ?
Comment 7 Timo Jyrinki 2023-12-13 18:45:59 UTC
Only aarch64 it seems.
Comment 8 Antonio Feijoo 2023-12-15 07:14:56 UTC
(In reply to Franck Bui from comment #6)
> Is this issue also happening x86_64 ?

My Fedora vm is x86_64
Comment 9 Franck Bui 2023-12-22 14:28:10 UTC
I submitted sr#316279.

It contains:

>  963d838bad vconsole-setup: handle the case where the vc is in KD_GRAPHICS mode more gracefully (bsc#1215282)

that should fix the current issue as well, assuming that it is a duplicate of bsc#1215282.

Timo maybe you can give this SR a try, just to confirm ?

Otherwise I'll close the bug as duplicate and you'll reopen it if the openqa test is still failing.
Comment 10 Timo Jyrinki 2023-12-28 13:49:58 UTC
The Tumbleweed started to be fixed as of 20231221 (and newer).

I think this is likely a duplicate indeed and let's just reopen it if it turns out the next SLE build it's still failing despite this having landed (it has not yet).

*** This bug has been marked as a duplicate of bug 1215282 ***