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 1997296 - isolinux does not properly handle backspaces or line wraps on the "boot:" menu
Summary: isolinux does not properly handle backspaces or line wraps on the "boot:" menu
Keywords:
Status: CLOSED DUPLICATE of bug 1748014
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: syslinux
Version: 8.4
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-24 21:05 UTC by Ryan Mullett
Modified: 2021-09-22 03:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-10 01:43:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-94691 0 None None None 2021-08-24 21:07:35 UTC

Description Ryan Mullett 2021-08-24 21:05:43 UTC
Description of problem:
When booting RHEL 8.4 ISO and using the boot: menu line wraps are not handled properly, and show as if there is a carriage return when there is not. Additionally, using backspace causes the console to refresh and show a whole separate line instead of simply removing the character off of the existing line

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

How reproducible:
Always

Steps to Reproduce:
For carriage return issue:
1. Boot system with RHEL 8.4 ISO
2. Press "escape" in order to get to the "boot:" menu
3. Hit a single character and continue to hold, eventually it will cause the system to show as if a carriage return was entered. This seems to usually happen shortly after hitting the end of screen and returning to the start

For the backspace issue:
1. Follow steps from carriage return issue above
2. Hit backspace, note that every time backspace is hit the screen refreshes and shows an entirely new entry

Actual results:
Display issues are seen, though they do not actually affect functionality. Even when the carriage return is displayed, there is not truly a carriage return, and functionality is normal. 

Expected results:
There are no fake carriage returns displayed, and backspace is handled properly within the same line instead of doing a full refresh on the console with a new line

Additional info:
Issue is not present on RHEL 7

I'm aware that this may not be an issue in anaconda necessarily, and could be an issue in ISOLINUX directly, but I don't see that as an available component. 

This has been reproduced thus far on kvm, as well as on vmware, so it is not yet confirmed if the issue is hit on all hardware. 

The functionality is not affected, and in all instances the boot: menu is still able to function normally to boot a system as expected, but this behavior does cause confusion when attempting to add parameters.

Comment 1 Robbie Harwood 2021-09-10 01:43:25 UTC

*** This bug has been marked as a duplicate of bug 1748014 ***


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