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:
There's a logic bug here In function startX at pyanaconda/core/util.py
the program triggers a timeout and executes sigalrm_handler When the Xorg service starts too slowly and exceeds the timeout time, which executes the raise exiterror causing the finally block to be executed.
The finally block will cancel processing of the SIGUSER1 signal, which will cause the signuser1 sent to Anaconda after the Xorg service is started to fail to process and the program will die
Version-Release number of selected component (if applicable):
anaconda 33.17
How reproducible:
In the function startX add code `time.sleep(0.5)` after the code `signal.alarm(timeout)` and add boot options: inst.xtimeout=1
Steps to Reproduce:
1. add code `time.sleep(0.5)` after the code `signal.alarm(timeout)` in function startX
2.make a new setup iso
3.add boot options: inst.xtimeout=1
Actual results:
X startup failed, falling back to text mode
Pane is dead(signal 10, date)
Expected results:
X startup failed, falling back to text mode
no other failed and i can setup os through text mode
Additional info:
NA
Looks like this bug was from the beginning for RHEL 8, although I treated it as for Rawhide. Sorry. That means all links above are upstream only. But from now on, let's keep it for RHEL 8.
Tested with anaconda 33.16.5.2-1.el8
If network is enabled, ip=dhcp on kernel cmdline, it works as expected.
Anaconda informs that X did not start and offers to continue installation via VNC or text mode.
If network is not enabled, anaconda throws exception and user cannot continue with the installation.
See attached logs.
After discussion and more testing we found that the reproduction steps were causing unrelated issue.
Pre-verified - anaconda 33.16.5.2-1.el8 in RHEL-8.5.0-20210524.t.19
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 (anaconda 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-2021:4254
Description of problem: There's a logic bug here In function startX at pyanaconda/core/util.py the program triggers a timeout and executes sigalrm_handler When the Xorg service starts too slowly and exceeds the timeout time, which executes the raise exiterror causing the finally block to be executed. The finally block will cancel processing of the SIGUSER1 signal, which will cause the signuser1 sent to Anaconda after the Xorg service is started to fail to process and the program will die Version-Release number of selected component (if applicable): anaconda 33.17 How reproducible: In the function startX add code `time.sleep(0.5)` after the code `signal.alarm(timeout)` and add boot options: inst.xtimeout=1 Steps to Reproduce: 1. add code `time.sleep(0.5)` after the code `signal.alarm(timeout)` in function startX 2.make a new setup iso 3.add boot options: inst.xtimeout=1 Actual results: X startup failed, falling back to text mode Pane is dead(signal 10, date) Expected results: X startup failed, falling back to text mode no other failed and i can setup os through text mode Additional info: NA