Bug 156052

Summary:	[ja] missing bterm font warning at boot time
Product:	[Fedora] Fedora	Reporter:	Jens Petersen <petersen>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	eng-i18n-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-04-28 17:20:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	136450

Description Jens Petersen 2005-04-27 02:20:47 UTC

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-27 03:21:59 UTC

The actual line on the console is something like

"Setting default font (bterm): Can't find font bterm."

Comment 2 Jens Petersen 2005-04-27 03:28:57 UTC

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 05:46:05 UTC

Chris, can you take a look at this tomorrow?

Comment 4 Chris Lumens 2005-04-27 14:29:21 UTC

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 20:00:38 UTC

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 20:50:01 UTC

Fixed in CVS.