Bug 24368

Summary:	systemd-vconsole-setup: KD_FONT_OP_GET Invalid argument
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Base system maintainers <basesystem>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	geiger.david68210, luigiwalser, mageia, mageia, marja11, ngompa13, pterjan, smelror, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	systemd-241-0.2.mga7.src.rpm	CVE:
Status comment:

Description Bit Twister 2019-02-16 10:41:10 CET

Description of problem: mga7 beta2

systemd-vconsole-setup[537]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
(Note that use of the override may cause unknown side effects.)



Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. clean mga7 cauldron plus updates
2. journalctl | grep failed

Comment 1 Marja Van Waes 2019-02-17 09:23:51 CET

Confirming the issue on an existing cauldron, last updated less than 1½ days ago, installed on May 13, 2018, where "-- Logs begin at Sun 2018-05-13 18:45:13 CEST, end at Sun 2019-02-17 08:33:12 CET. --"

The first instance is one second later than logs begin:

mei 13 18:45:14 localhost systemd-vconsole-setup[513]: KD_FONT_OP_GET failed while trying to get the font metadata: Ongeldig argument

last 2 instances were while last booting the system, this morning.

● systemd-vconsole-setup.service - Setup Virtual Console
   Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
   Active: inactive (dead) since Sun 2019-02-17 08:04:24 CET; 58min ago
     Docs: man:systemd-vconsole-setup.service(8)
           man:vconsole.conf(5)
  Process: 736 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS)
 Main PID: 736 (code=exited, status=0/SUCCESS)

feb 17 08:04:24 localhost systemd[1]: Starting Setup Virtual Console...
feb 17 08:04:24 localhost systemd[1]: Started Setup Virtual Console.

Assigning to the basesystem maintainers, CC'ing a bunch of committers and the registered maintainer. 

I felt tempted to CC no one, because I thought this is little more than a cosmetic issue (my VTs work fine), but then realized I do _not_ know.

CC: (none) => geiger.david68210, luigiwalser, mageia, mageia, marja11, ngompa13, pterjan, smelror, tmb
Assignee: bugsquad => basesystem

Comment 2 Bit Twister 2019-02-17 13:28:58 CET

(In reply to Marja Van Waes from comment #1)
 
> I felt tempted to CC no one, because I thought this is little more than a
> cosmetic issue (my VTs work fine), but then realized I do _not_ know.

I understand where you are coming from, but if designer/coder goes to
the effort to code warnings/errors checks let alone unknown side effects
I suggest it needs attention.

After a few months of experience as a maintenance coder, I found it paid
off in the long run to fix _all_ faults prior to actually hunting down
a reported bug on any new software I was to maintain.

Unknown side effects seem to become security exploits. :(

It is also nice when any monitoring scrip comes up with no problems found
in logs.  :)

Comment 3 Thomas Backlund 2019-02-17 16:30:06 CET

IIRC this has been seen before and it's basically a timing issue..

So it's not a critical issue, but we'll try to get it fixed

Comment 4 Bit Twister 2019-02-19 12:42:13 CET

Latest updates with kernel 4.20.10-desktop-2.mga7 no longer have the problem.

Comment 5 Bit Twister 2019-02-19 12:42:39 CET

Sorry forgot to hit resolved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED