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.
DescriptionAnssi Johansson
2015-06-25 10:30:38 UTC
Created attachment 1043050[details]
Screen shot of the bug
Description of problem:
Most of the texts for text mode "initial setup" are shown in English, even if the user has chosen to use something else than English as the language during installation.
The user is presented with "Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]", regardless of the language selected.
However, the 'c' option is not accepted. Instead, the user is required to enter the first letter of the word "continue" in their own language. For example, "continue" in Finnish is "jatka", so 'j' works. In Swedish, "continue" is "fortsättä", so 'f' works.
Version-Release number of selected component (if applicable):
initial-setup-0.3.9.23-1.el7.centos.2.x86_64.rpm
How reproducible:
Always
Steps to Reproduce:
1. Do a minimal install in Finnish (or presumably any other non-English language)
2. yum install initial-setup
3. reboot
Actual results:
initial-setup asks for 'c', but accepts only 'j'. See the attached screen shot.
Expected results:
The prompt should match the key the user is supposed to press.
Additional info:
This was tested on CentOS 7.1.1503, but I have reason to believe this also affects RHEL. Bug 1183042 may have an effect in reproducing this bug. In fact, we do exactly that in CentOS 7 nowadays, so the "steps to reproduce" no longer work for CentOS.
Best regards, avij from the CentOS QA team
Looks like this issue is actually a result of how the Anaconda text mode translations are done. The translation of the "Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]" string is done separately from the translations of the "q", "c" and "r" strings.
So if one of them os translated and the other is not the results is that we tell the user he should type something while expecting him to type something else.
The solution for this is to not depend on the translations to be complete by translating the trigger letters separately:
"Please make your choice from above ['%s' to quit | '%s' to continue | '%s' to refresh]" % (_("q"), _("c"), _("r"))
In this case a partial translation might look weird (the letter might be translated but the overall message not) but it will always expect the user to type the same letter that is actually displayed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2284.html