Bug 75564

Summary: Default font not applied to all virtual consoles
Product: [Retired] Red Hat Linux Reporter: Carlos Rodrigues <cefrodrigues>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:49:48 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:

Description Carlos Rodrigues 2002-10-09 21:52:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
After changing the locale to a non utf8 one (because unicode seems broken to 
me in many ways, already reported here in bugzilla) I also changed the console 
font to lat9-16 (SYSFONT="lat9-16" in /etc/sysconfig/i18n). But now this font 
is only applied to the first virtual console and not the other ones. In 7.3 
this worked fine.

How reproducible:
Always

Steps to Reproduce:
1.in /etc/sysconfig/i18n change the default locate to, say, pt_PT.iso885915
2.change the default font to lat9-16
3.reboot just to make sure
	

Actual Results:  After the system is back up, only the first virtual console 
uses the correct font, you cah check this by trying to use an accented 
character at the login prompt

Expected Results:  The font should be applied to all vt's like it used to 
happen in 7.3.

Comment 1 Eido Inoue 2003-02-19 21:09:05 UTC
font settings not being inherited by all the vts is a known kernel bug (or is it
a feature?)

Comment 2 Carlos Rodrigues 2003-09-07 02:22:54 UTC

*** This bug has been marked as a duplicate of 89446 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:48 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.