Red Hat Bugzilla – Bug 1250262
Live images do not use eurlatgr console font by default
Last modified: 2017-07-31 13:09:09 EDT
To reproduce: boot a Fedora live image (22, 23 or Rawhide), go to tty2, log in as root, and run 'cat /usr/lib/kbd/consolefonts/README.eurlatgr'. Note all the greek characters are boxes.
The live images *do* have a correct /etc/vconsole.conf , but somehow it doesn't seem to be applied.
If you run '/usr/lib/systemd/systemd-vconsole-setup' from a tty after logging in, eurlatgr gets loaded in all TTYs. However, it's clear that the systemd-vconsole-setup.service service *did* run during boot, if you check systemctl output. If you boot with systemd.log_level=debug you can see from the messages that it seems to run properly, so far as I can see.
So...I'm not sure what's going on? Timing issue? Something more subtle?
This isn't going to be noticeable for a lot of people, I guess, but it gives us a bit of a problem with openQA - as we do matching on console screenshots, we kinda want the font used to be consistent between the live environment, anaconda environment, and installed system environment.
This looks like a timing issue. I can reproduce this on a virtual machine with about 33% chance (using 4 CPUs). And the less CPUs I allocate for the VM, the less likely it seems to happen.
Odd - it seemed to happen on all my tests and I only have 2 CPUs assigned to the virt guest. I'll try it a few more times tomorrow.
Just for the record, I use the following to run the VM:
$ qemu-system-x86_64 -enable-kvm -m 2G -smp cpus=4 -cdrom Fedora-Live-Workstation-x86_64-23-20150804.iso
https://bugzilla.redhat.com/show_bug.cgi?id=1074624 was about fonts not taken into use but not sure had vconsole-setup been rerun already in your case.
If you tail README.eurlatgr from kbd-2.0.3 (or grab it from ), you should be at least able to determine which font is in use at that time.
I'm fairly sure it's just the firmware font. i.e. it's not that any other font has been loaded - no font has been loaded, and the system's still using the firmware one.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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'
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 24 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.
This seems to be fixed in Fedora 26.