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 601101 - specifying language in the kernel command line makes accented characters broken
Summary: specifying language in the kernel command line makes accented characters broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ales Kozumplik
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-07 08:38 UTC by Ales Kozumplik
Modified: 2014-09-30 23:39 UTC (History)
3 users (show)

Fixed In Version: anaconda-13.21.51-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 19:47:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
broken accented characters (6.85 KB, application/octet-stream)
2010-06-07 08:38 UTC, Ales Kozumplik
no flags Details
screenshot with snapshot #7 (6.87 KB, image/png)
2010-07-06 10:37 UTC, Alexander Todorov
no flags Details

Description Ales Kozumplik 2010-06-07 08:38:00 UTC
Created attachment 421749 [details]
broken accented characters

Steps to Reproduce:
1. start installation with lang=cs_CZ command line option
2. ??
3. profit!
  
Actual results:
some accented characters broken or missing, see the screen capture.

Expected results:
no such artifacts are visible, like when one chooses the language from a menu.

Additional info:
This could be the same problem as bug 576541.

Comment 2 RHEL Program Management 2010-06-07 17:05:17 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Ales Kozumplik 2010-06-10 14:55:17 UTC
Fixed by 0e44fbc1589a91dacefff78341a34c12b782c7f5 in anaconda-31.21.51-1.el6.

Comment 5 Alexander Todorov 2010-07-06 10:37:15 UTC
Created attachment 429738 [details]
screenshot with snapshot #7

I've tested this with snap #7 (0701.3) which has anaconda-13.21.56-1.el6.

Booted with lang=cs_CZ parameter and performed the install in text mode. I didn't see any garbled characters, text output was looking correct. See attached screenshot which shows the fix (compare to previous screenshot). 

Moving to VERIFIED.

Comment 6 releng-rhel@redhat.com 2010-11-10 19:47:07 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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