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.

Description of problem:

The text mode of the installer shows multiple virtual consoles (outlining the storage log, etc.) but doesn't mention that you need to hit "Control-B #" to get to the different virtual consoles.  A tool tip here would be very useful.

Version-Release number of selected component (if applicable):
anaconda-19.31.77-1.el7


How reproducible:
everytime

Steps to Reproduce:
1. start text mode installatoin

Actual results:
No message about CTRL-B present

Expected results:
Add "tip" about CTRL-B usage

Well, this is just tmux here so it's the same key sequences as it provides.  I believe the best place to explain this would be in documentation.  Tooltips don't really make sense as a concept in the UI we've got to work with.