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:
When changing /etc/issue to use the \l control code (which presents the tty the getty is running on), it shows as a dash (-) instead of tty1. This behavior differs from RHEL 8 and current Fedora.
This may be due to the change to using the stdin file descriptor to determine the tty.
agetty --show-issue shows expected results (though likely just as an example for the user)
Version-Release number of selected component (if applicable):
This occurs on 9.0 and CentOS Stream 9.
How reproducible:
Always
Steps to Reproduce:
1. Modify /etc/issue and include \l...
2c2
< Kernel \r on an \m
---
> Kernel \r on an \m (\l)
2. systemctl restart getty (or logout if already on tty1 console, or switch to tty2/tty3/etc)
Actual results:
Red Hat Enterprise Linux 9.0 (Plow)
Kernel 5.14.0-70.17.1.el9_0.x86_64 on an x86_64 (-)
CentOS Stream 9
Kernel 5.14.0-119.el9.x86_64 on an x86_64 (-)
Rocky Linux 9.0 (Blue Onyx)
Kernel 5.14.0-70.17.1.el9_0.x86_64 on an x86_64 (-)
Expected results:
Running tty is shown, similar to Fedora.
Fedora Linux 36 (Thirty Six)
Kernel 5.18.7-200.fc36.x86_64 on an x86_64 (tty1)
Additional info:
This was reported at the Rocky Linux bug tracker: https://bugs.rockylinux.org/view.php?id=156 and confirmed on a RHEL 9.0 and CentOS Stream 9 system.