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.
Description of problem:
The nmuti TUI could be killed by using combinationkey. (ESC+one of the Arrow)
Version-Release number of selected component (if applicable):
rhel-server-7.2-x86_64-dvd.iso
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
How reproducible:
Steps to Reproduce:
1.Install the OS with the iso
2.use nmtui tool to config the NIC
3.at any screen of this scrreen
4.Press the ESC and then any of the Arrow keys
Actual results:
Get me out of the nmtui
Expected results:
I may should still stay in the nmtui tool
Additional info:
Steps to Reproduce:
1.Install the OS with the iso
2.use nmtui tool to config the NIC
3.at any step of these screen
4.Press the ESC and then any of the Arrow keys
Comment 3Beniamino Galvani
2016-10-06 07:50:00 UTC
nmtui registers a hotkey for ESCAPE in this way:
newtFormAddHotKey (priv->form, NEWT_KEY_ESCAPE);
but it seems that the newt library generates the same code for all
unknown combinations as:
ESC + letter
ESC + arrow
CTRL + arrow
...
For all these, newtExitStruct.u.key has the value 27 (ESC), so there
is no way nmtui can distinguish them from a real ESC press.
Reassigning to newt component for analysis.
Terminals don't support escape as a key modifier and there is no special sequence for such combinations. From the application point of view, escape + arrow key is the same as pressing escape and then arrow key. For example in xterm escape+left emits ^[^[OD, which is the same as pressing them sequentially.
To me it looks it's working as expected.
Comment 5Beniamino Galvani
2016-10-07 13:04:22 UTC
(In reply to Miroslav Lichvar from comment #4)
> Terminals don't support escape as a key modifier and there is no special
> sequence for such combinations. From the application point of view, escape +
> arrow key is the same as pressing escape and then arrow key. For example in
> xterm escape+left emits ^[^[OD, which is the same as pressing them
> sequentially.
For the key combinations containing ESC, your explanation makes perfectly sense to me. However I noticed that all these other combinations are also handled as ESC and make nmtui quit; is this correct?
ALT + letter
CTRL + (arrow, ins, canc, pg-up, pg-down, ...)
CTRL + function keys
For example, ALT+o emits ^[o which is \033o; that could be easily distinguished from ^[, no?
(In reply to Beniamino Galvani from comment #5)
> For example, ALT+o emits ^[o which is \033o; that could be easily
> distinguished from ^[, no?
Yes, if the newt's database contained such escape sequence. There are no NEWT_KEY_* constants defined in newt.h for these combinations, so the header would have to be expanded too.