Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1688332

Summary: Text interface on VT/kernel console broken for non-latin languages
Product: Red Hat Enterprise Linux 8 Reporter: Martin Kolman <mkolman>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: jstodola, lijli, vslavik
Target Milestone: rcKeywords: i18n
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-01 07:39:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Japanese characters shown as squares in the TUI on a VT. none

Description Martin Kolman 2019-03-13 14:50:54 UTC
Created attachment 1543685 [details]
Japanese characters shown as squares in the TUI on a VT.

Description of problem:
The Anaconda text interface is broken for some non-latin languages (such as Japanese) when running on a virtual terminal (kernel console). Serial consoles are apparently unaffected and can display at least Japanese just fine.

Version-Release number of selected component (if applicable):
29.19.0.38-1

How reproducible:
always

Steps to Reproduce:
1. start the installation withe these boot options added:
inst.lang=ja_JP inst.text

Actual results:
The virtual terminal shows squares in place of Japanese characters. Serial console looks fine.

Expected results:
The virtual terminal falls back to English instead of showing squares. If serial console is used, fallback to English is not activated.

Additional info:
This was fixed in RHEL 7 in the past (bzg 1182562), but the fix has likely regressed since then.

Comment 3 RHEL Program Management 2021-02-01 07:39:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 4 Vladimír Slávik 2021-05-06 12:11:58 UTC
The reason for this is most probably that fonts are not (re)loaded. For actual technical details that would likely lead to a fix, see https://github.com/rhinstaller/anaconda/pull/3304#issuecomment-832070115 Note that loading fonts changes screen size, so it's not a straightforward fix.