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 1364539

Summary: In some cases the TUI user is told to press a key but a different key is expected
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kolman <mkolman>
Component: anacondaAssignee: Jiri Konecny <jkonecny>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: jkonecny, jstodola, jvavra, mkolaja, mkolman, sbueno
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-21.48.22.87-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 23:26:37 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:

Description Martin Kolman 2016-08-05 16:08:11 UTC
Description of problem:
Due to a translation error (the expected key is not translated) there are cases where the user is told to press a key (say p for Pokračovat) but a different key is expected by the TUI (c for continue). The prompt is translated but the expected key is not.

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


How reproducible:
always

Steps to Reproduce:
1. start a text installation in a non English language with good coverage (say Czech)
2. enter the storage configuration spoke (Cíl instalace)
3. sleect some option, such as "use all"
4. inoput the continue key (p in Czech)
5. press enter

Actual results:
TUI switches to the hub. If c is pressed the TUI advances to the next screen in the storage configuration spoke, demonstrating that the issues is caused by incorrect translations.


Expected results:
TUI switches to the next screen in the storage configuration spoke

Additional info:
On a cursory look, these places should be fixed but there might be other places in the code with the same issues:

pyanaconda/rescue.py:301:            if key.lower() == "c":
pyanaconda/ui/tui/spokes/software.py:153:            if key.lower() == "c" and 0 <= self._selection < len(self.payload.environments):
pyanaconda/ui/tui/spokes/source.py:460:        if key == "c":
pyanaconda/ui/tui/spokes/storage.py:269:            if key.lower() == "c":
pyanaconda/ui/tui/spokes/storage.py:521:            if key.lower() == "c":
pyanaconda/ui/tui/spokes/storage.py:572:            if key.lower() == "c":

Comment 4 Jakub Vavra 2016-09-06 13:02:19 UTC
This specific issue seems to be fixed and I did not encounter it during the install. Similar issue may be on other places but I did not hit it.

Verified on RHEL-7.3-20160901.1.

Comment 6 errata-xmlrpc 2016-11-03 23:26:37 UTC
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/RHEA-2016-2158.html