Created attachment 822812 [details]
screenshot of the problem
Description of problem:
The default console font is not able to display all the needed characters.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. I tried to boot in rescue mode (removing "rhgb", "quiet", adding "single")
see the screenshot - at the bottom there is sentence
"Pro zah?jen? ?dr?by je t?eba zadat heslo u?ivatele root"
it should be
"Pro zahájení údržby je třeba zadat heslo uživatele root"
I'm not sure if this is problem of the font itself or some console translation, as after logging in, I'm getting squares instead of some characters, not the question marks as in the screenshot ...?
The default console font is "latarcyrheb-sun16" as far as I know and it should be able to display all needed characters.
This font is shipped within kbd, but I do not know which component is responsible to set it in this phase of booting.
You can do it manually with "setfont latarcyrheb-sun16" command.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Created attachment 977431 [details]
(In reply to Vitezslav Crhonek from comment #2)
> This font is shipped within kbd, but I do not know which component is
> responsible to set it in this phase of booting.
now the question is ... is _anything_ actually trying to to set it in this phase?
I'd say it should be systemd-vconsole-setup.service which is required by sysinit.target which is required by rescue.target which is reached before the password prompt ...
FTR, the problem still persists with RHEL-7.1-20150107.n.0 - and in addition, there are some random characters scattered all over the screen
This should be reassigned to different component, which is responsible for setting correct font, keymap, etc. when booting to rescue mode. I don't know for sure which one is it.
kbd is just a bunch of fonts, keymaps and tools for setting them, but it has no logic in it, it's supposed to be called by other programs and scripts. And it contains fonts with non-ascii support.
Changing component to systemd as Karel suggested in comment#4. Feel free to change it again, if it's wrong component.
This problem is probably two different problems.
First one is that the font specified in /etc/vconsole.conf is not loaded at all. That can be verified by executing "loadkeys cz" and then typing the first row on the keyboard. But, even after the font has been loaded, the message is still not displayed properly.
The second problem is the actual display of the message.
The service that I have created to do the font setting is posted below. For some reason, modifying systemd-vconsole-setup to be run before rescue.target didn't work.
# systemctl cat vconsole-workaround.service
There is probably something wrong with how sulogin handles the output (and perhaps even the terminal):
# LANG=cs_CZ.UTF-8 gettext -e util-linux "Give root password for maintenance\n"
Pro zahájení údržby je třeba zadat heslo uživatele root
# LANG=cs_CZ.UTF-8 gettext -e util-linux "(or press Control-D to continue): "
(nebo stiskněte Control-D, abyste pokračovali):
# LANG=cs_CZ.UTF-8 sulogin
Pro zah?jen? ?dr?by stiskn?te Enter(nebo stiskn?te Control-D, abyste pokra?ovali):
(In reply to Jan Synacek from comment #9)
> # LANG=cs_CZ.UTF-8 sulogin
> Pro zah?jen? ?dr?by stiskn?te Enter(nebo stiskn?te Control-D, abyste
Well, you cannot do that with programs like agetty or sulogin on pseudo-terminals. If you try the same command on regular console that all will work as expected.
Anyway, the problem is how sulogin detects virtual console, the problem is fixed in the current upstream tree (I'm not able to reproduce it with sulogin from v2.27). The best will be to rebase sulogin.c to the latest upstream, we have more fixes there.
CC myself & severity to medium - this impacts remote debugging if user cannot read console errors in their native tongue.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
Created attachment 1205173 [details]
before the fix
Created attachment 1205174 [details]
after the fix
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.