Bug 1640176 - systemd-vconsole-setup[nnn]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
Summary: systemd-vconsole-setup[nnn]: KD_FONT_OP_GET failed while trying to get the fo...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 33
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-17 13:40 UTC by Generic User
Modified: 2021-11-30 17:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:53:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd issues 6689 0 None open vconsole: if KD_FONT_OP_SET fails (maybe because X11/wayland/some display manager are blocking tty7), debug log and proc... 2021-02-02 17:20:51 UTC

Description Generic User 2018-10-17 13:40:48 UTC
Description of problem:
Examination of journal logs shows that this failure happens at each boot:
systemd-vconsole-setup[396]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented 

Version-Release number of selected component (if applicable):
systemd-238-9.git0e0aa59.fc28.x86_64

How reproducible:
On each boot.

Steps to Reproduce:
1. Boot
2. Examine journal logs (journalctl -b)
3.

Actual results: [redacted journal log segment]
Oct 17 04:58:23 <hostname> systemd-vconsole-setup[396]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
Oct 17 04:58:23 <hostname> systemd-vconsole-setup[396]: Fonts will not be copied to remaining console

Expected results:
No failures.

Additional info:

Comment 1 Zbigniew Jędrzejewski-Szmek 2018-10-17 13:48:51 UTC
What kernel are you using?

Comment 2 Generic User 2018-10-17 14:49:26 UTC
# uname -r
4.18.13-200.fc28.x86_64

Comment 3 Ben Cotton 2019-05-02 20:37:56 UTC
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.

Comment 4 Ben Cotton 2019-05-28 18:56:05 UTC
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.

Comment 5 mark preston 2020-05-30 14:19:16 UTC
still an issue and so it still needs addressing instead of ignoring.

Comment 6 Ben Cotton 2020-11-03 17:11:48 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.

Comment 7 mark preston 2020-11-06 00:04:48 UTC
upgraded to 33 and the error is still in my messages file still an issue still not fixed

Comment 8 Zbigniew Jędrzejewski-Szmek 2021-02-02 17:22:40 UTC
(In reply to mark preston from comment #5)
> still an issue and so it still needs addressing instead of ignoring.

Well, it was set to MODIFIED, which means nobody would ever look at it.

Comment 9 Ben Cotton 2021-11-04 16:09:34 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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.

Comment 10 Ben Cotton 2021-11-30 17:53:46 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.


Note You need to log in before you can comment on or make changes to this bug.