Bug 2238995

Summary: Installer crashes when starting chronyd service
Product: [Fedora] Fedora Reporter: Onyeibo Oku <onyeibo>
Component: anacondaAssignee: anaconda-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 40CC: anaconda-maint, kkoukiou, vslavik, w
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-16 14:31:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Syslog none

Description Onyeibo Oku 2023-09-14 17:27:03 UTC 
Installer crashed after showing cursor (pointer). It displays a message box with traceback indicating that Anaconda encountered an error.  

Reproducible: Always

Steps to Reproduce:
1. Download ISO from https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20230914.n.0/compose/Server/x86_64/iso/Fedora-Server-netinst-x86_64-Rawhide-20230914.n.0.iso
2. Make a USB install media using Fedora Media Writer
3. Boot with Media
Actual Results:  
Booting proceeds until the message box shows

Expected Results:  
I expected to see the Graphical Installer (set timezone, repository, package group, partitions etc.)

The traceback ends with the following lines

File "/usr/lib64/python3.12/site-packages/pyanaconda/core/service.py", line 53 in start_service
    return_run_systemctl("start", service, "/")
File "/usr/lib64/python3.12/site-packages/pyanaconda/startup_utils.py", line 469 in start_chronyd
    start_service("chronyd")
File "/sbin/anaconda", line 547, in <module>
    startup_utils.start_chronyd()
pyanaconda.errors.ExitError: gnome-kiosk exited on signal 5
Comment 1 Onyeibo Oku 2023-09-14 17:30:17 UTC 
I got the same result with Fedora-Server-netinst-x86_64-Rawhide-20230912.n.0.iso and Fedora-Server-netinst-x86_64-Rawhide-20230913.n.0.iso

Machine: Dell Optiplex 3050
Comment 2 Vladimír Slávik 2023-09-19 14:19:58 UTC 
Thank you for the report. The gnome-kiosk crashes are usually unrelated to the traceback seen, as the whole program stops at a random place in a random thread.

Can you please provide some logs, preferably journal and/or syslog? They should be dumped into /tmp at the crash time.
Comment 3 Onyeibo Oku 2023-09-19 17:05:06 UTC 
(In reply to Vladimír Slávik from comment #2
> Can you please provide some logs, preferably journal and/or syslog? They
> should be dumped into /tmp at the crash time.

Please advise on how export the logs placed at /tmp. As at the time of crashing, I could not find a way to access a shell. Anaconda presents the option of debugging which gives me a terminal session. When I exit that session, I am back to a GUI session.  Is there a way to drop to shell?
Comment 4 Onyeibo Oku 2023-09-21 11:11:49 UTC 
Created attachment 1989821 [details]
Syslog
Comment 5 Aoife Moloney 2024-02-15 22:57:50 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.
Comment 6 Katerina Koukiou 2024-04-16 14:31:50 UTC 

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