From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: I'm not using an utf-8 locale (because I lose the accented characters in the console, bug #75430) and thus I am defining another font for the console. The problem is that this font is not loaded on vt's other than the first. I see that for unicode locales, /etc/profile.d/lang.sh takes care of loading $SYSFONT on the other vt's but if the locale is not unicode this does not happen. How reproducible: Always Additional info: The contents of /etc/sysconfig/i18n: LANG="en_US" SUPPORTED="en_US.UTF-8:en_US:en:pt_PT.UTF-8:pt_PT:pt" SYSFONT="lat9w-16" CHARSET="8859-15" LC_COLLATE="pt_PT@euro" LC_CTYPE="pt_PT@euro" LC_MONETARY="pt_PT@euro"
Created attachment 93182 [details] loads console font even when the locale is not unicode I changed the lang.sh and lang.csh scripts a bit to load the default console font even when the locale is not unicode.
This shouldn't be necessary; what problem are you seeing without this? Fonts don't really need to be called for each console; setting it once should suffice (the reason unicode_start is called is because there are other issues that it takes care of.)
I'm defining the font lat9w-16 for the console because it has accented characters (like á for instance). But (without my changes to lang.sh) it is only defined for the first vt, so, if I press "´ + a" in the first vt I see "á", but if I do the same in the other vt's I see "a".
I made a little mistake in my previous comment. Actually "á" (á) displays ok but some characters which have a tilde - like "ã" (ã) and "õ" (õ) do not. Besides this small detail (maybe next time I will reproduce the problem again instead of trusting my memory of it) my point remains the same.
*** Bug 75564 has been marked as a duplicate of this bug. ***
Closing bugs on older, no longer supported, releases. Apologies for any lack of response. I suspect this was due to a kernel bug, which we worked around in previous releases. The kernel bug was fixed in 2.6.13 and later.