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 1748014 - Glitches in line editor
Summary: Glitches in line editor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: syslinux
Version: 8.7
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: rc
: 8.0
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL: https://www.syslinux.org/archives/202...
Whiteboard:
: 1997296 (view as bug list)
Depends On:
Blocks: 2018260
TreeView+ depends on / blocked
 
Reported: 2019-09-02 13:27 UTC by Mason Loring Bliss
Modified: 2024-12-20 18:53 UTC (History)
11 users (show)

Fixed In Version: syslinux-6.04-6.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2018260 (view as bug list)
Environment:
Last Closed: 2022-11-08 10:56:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTT-4729 0 None None None 2022-08-03 12:42:13 UTC
Red Hat Issue Tracker RTT-4730 0 None None None 2022-08-03 12:42:19 UTC
Red Hat Product Errata RHBA-2022:7806 0 None None None 2022-11-08 10:56:43 UTC

Description Mason Loring Bliss 2019-09-02 13:27:16 UTC
Description of problem:

Booting the RHEL 8 ISO, if the user hits escape to access the boot prompt, as
happens, for example, when kickstarting from the ISO, long lines will force an
unusual wrap that includes an extra, cosmetic newline. Backspace then redraws
the whole line, but will position the cursor after a phantom space that doesn't
exist in the actual input buffer.

How reproducible:

Boot RHEL 8 ISO in KVM/QEMU, ESC, enter a long command line.


Steps to Reproduce:

1. Boot RHEL 8 ISO.
2. Hit escape prior to automatic boot.
3. Enter this all on one line:

linux 1234567890x1234567890x1234567890x1234567890x1234567890x1234567890x1234567890x1234567890x1234567890

4. On wrap, backspace and note the odd behaviour.
5. Use ^L to refresh the screen, showing that what was displayed was not in fact
the content of the input buffer.

Additional info:

^U and ^L work and can help manipulate and show the actual buffer content. The
customer bringing this issue to us enters longish kickstart sepecifiers and has
been thrown off by the formatting, which introduces errors. There's still
some chance they're seeing actual erroneous input passed through, generated by
the line editor's wrapping bug, but I'm assuming it's purely cosmetic until we
can identify and reproduce a hard error.

Comment 2 Mason Loring Bliss 2019-11-25 14:33:59 UTC
This has been sitting idle for an awfully long time. Please advise.

Comment 3 Jan Hlavac 2019-12-13 17:47:08 UTC
Hello,

I successfully reproduced the bug. It seems to be a bug in Syslinux that is used when the installation media is booted in the BIOS/Legacy mode.

A possible workaround is to switch the system from the BIOS/Legacy to the UEFI mode where GRUB 2 is used instead of Syslinux.

Now I am trying to find the cause of the bug.

Comment 8 Robbie Harwood 2021-09-10 01:43:25 UTC
*** Bug 1997296 has been marked as a duplicate of this bug. ***

Comment 19 Marta Lewandowska 2022-08-26 12:03:31 UTC
Verified using nightly RHEL-8.7.0-20220825.2-x86_64-boot.iso, which contains syslinux-6.04-6.el8.x86_64.rpm

Comment 21 errata-xmlrpc 2022-11-08 10:56:40 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 (syslinux bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:7806


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