-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
rhel-10.1
-
No
-
Moderate
-
rhel-anaconda
-
None
-
False
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Pressing Ctrl+C in Anaconda in text mode makes it crash. There's a similar issue in RHEL-118821, but based on the traceback, it has a different root cause.
anaconda 40.22.3.33-1.el10_1 for Red Hat Enterprise Linux 10.1 (pre-release) started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2) * if the graphical installation interface fails to start, try again with the inst.text bootoption to start text installation * when reporting a bug add logs from /tmp as separate text/plain attachments ================================================================================ ================================================================================ Text mode provides a limited set of installation options. It does not offer custom partitioning for full control over the disk layout. Would you like to use remote graphical access via the RDP protocol instead? 1) Use graphical mode via Remote Desktop Protocol 2) Use text mode Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to refresh]: ^CTraceback (most recent call last): File "/sbin/anaconda", line 470, in <module> display.setup_display(anaconda, opts) File "/usr/lib64/python3.12/site-packages/pyanaconda/display.py", line 346, in setup_display use_rd, credentials = ask_rd_question(anaconda, message) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.12/site-packages/pyanaconda/display.py", line 114, in ask_rd_question App.run() File "/usr/lib/python3.12/site-packages/simpleline/__init__.py", line 136, in run App.get_event_loop().run() File "/usr/lib/python3.12/site-packages/simpleline/event_loop/__init__.py", line 105, in run self._run() File "/usr/lib/python3.12/site-packages/simpleline/event_loop/main_loop.py", line 66, in _run self._mainloop() File "/usr/lib/python3.12/site-packages/simpleline/event_loop/main_loop.py", line 154, in _mainloop self._process_signals_loop() File "/usr/lib/python3.12/site-packages/simpleline/event_loop/main_loop.py", line 223, in _process_signals_loop signal = self._active_queue.get() ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/simpleline/event_loop/event_queue.py", line 96, in get return self._queue.get() ^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.12/queue.py", line 171, in get self.not_empty.wait() File "/usr/lib64/python3.12/threading.py", line 355, in wait waiter.acquire() File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 117, in _sigchld_handler cls._raise_exit_error(exit_statuses) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 81, in _raise_exit_error raise ExitError(", ".join(exn_message)) pyanaconda.errors.ExitError: systemd exited with status 0
As opposed to RHEL-118821, the traceback apparently happens on a much lower level (improper SIGINT handling?), as not even the anaconda-tb* file is generated when the traceback occurs.
What is the impact of this issue to you?
Potentially bad UX in text mode.
Please provide the package NVR for which the bug is seen:
anaconda-40.22.3.33-1.el10_1
How reproducible is this bug?:
Always.
Steps to reproduce
- Start installation in text mode.
- Hit Ctrl+C when Anaconda starts and displays its menu.
Expected results
Traceback.
Actual results
Nothing happens or the current prompt is printed anew.
- is related to
-
-
- Planning
-
