Bug 156052 - [ja] missing bterm font warning at boot time
[ja] missing bterm font warning at boot time
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Mike McLean
Depends On:
Blocks: FC4Blocker
  Show dependency treegraph
Reported: 2005-04-26 22:20 EDT by Jens Petersen
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-28 13:20:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jens Petersen 2005-04-26 22:20:47 EDT
Description of problem:
I'm not sure what the exact cause of this problem with for a while now
with recent trees, a warning is appearing on in the startup messages
on the console about not finding the bterm font.

How reproducible:
every time

Steps to Reproduce:
1. Boot rawhide install (in Japanese system locale?).
2. Look at boot messages on virtual console.
Actual results:
2. missing bterm font error message seen.

Expected results:
2. No error.
Comment 1 Jens Petersen 2005-04-26 23:21:59 EDT
The actual line on the console is something like

"Setting default font (bterm): Can't find font bterm."
Comment 2 Jens Petersen 2005-04-26 23:28:57 EDT
Actually "Can't find font file bterm".

This happens with even bogl-bterm installed fwiw.

I noticed that SYSFONT set in /etc/sysconfig/i18n to bterm:
not quite sure why though... so re-assigning to anaconda
for info.

[This is from a rawhide install last week, updated with yum.]
Comment 3 Jeremy Katz 2005-04-27 01:46:05 EDT
Chris, can you take a look at this tomorrow?
Comment 4 Chris Lumens 2005-04-27 10:29:21 EDT
SYSFONT is set to bterm because of the following line in anaconda's lang-table file:

Japanese        ja      bterm   ja_JP.UTF-8     jp106   Asia/Tokyo

Is bterm an incorrect setting?  Should SYSFONT not be getting specified?
Comment 5 Jeremy Katz 2005-04-27 16:00:38 EDT
We need bterm for use in the installer, but it's not valid for the general case.
 I think we used to do some munging to avoid bterm getting written out.
Comment 6 Chris Lumens 2005-04-27 16:50:01 EDT
Fixed in CVS.

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