Created attachment 1502035 [details] initial-setup logs Description of problem: After installing Fedora IoT, the system hangs at boot waiting for initial-setup, even when a user already exists and root password has been set during the installation. Version-Release number of selected component (if applicable): initial-setup-0.3.62-1.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Install IoT edition 2. reboot, boot will hang
Created attachment 1502036 [details] journalctl
Testing todays IoT compose with python3-3.7.1-2.fc29 and initial-setup-0.3.62-1.fc29, the boot still hangs waiting for initial-setup.
The 2018-11-06 IoT compose pulled in python3-3.7.1-2.fc29 as referenced in 1160259 as a possible fix to no effect. Looking at the anaconda-ks.cfg generated during install it's got the following line: # Run the Setup Agent on first boot firstboot --enable Which I don't believe should be there given that that the root password is set during install, and a user is created so the firstboot option should not be required.
Either this is fixed or I'm having a hard time reproducing this. I've tried with both x86_64 (VM) and aarch64 (RPI3). It boots correctly and I am able to use the firstboot to generate a user. I am using the images Fedora-IoT-29-20181114.0.aarch64.raw.xz Fedora-IoT-29-20181114.0.x86_64.raw.xz
(In reply to Troy Dawson from comment #4) > Either this is fixed or I'm having a hard time reproducing this. > I've tried with both x86_64 (VM) and aarch64 (RPI3). It boots correctly and > I am able to use the firstboot to generate a user. > I am using the images > Fedora-IoT-29-20181114.0.aarch64.raw.xz > Fedora-IoT-29-20181114.0.x86_64.raw.xz My testing indictaes all works fine (Initial Setup TUI shows up and can be used) if user is *not* created during the installation. But when user *is* created during the installation and Initial Setup is enabled, instead of Initial Setup detecting there is nothing for it to do it get's stuck for some reason.
Turns out this is caused by the text interface starting the TUI main loop even if no screens are scheduled to be shown. This happens in this case, as user has already been created so there is nothing to be shown, but the main loop will still be started, effectively waiting forever. As the parent TUI classes that handle the main loop startup are in Anaconda and Initial Setup only inherits them I'm reassigning this bug to Anaconda as the fix will have to go there.
PR: https://github.com/rhinstaller/anaconda/pull/1692
We found a better solution in the python-simpleline project. That is used for the text user interface in the Initial Setup and Anaconda.
PR: https://github.com/rhinstaller/python-simpleline/pull/59
initial-setup-0.3.62-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9bf4608fa
initial-setup-0.3.62-2.fc29, python-simpleline-1.4-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9bf4608fa
Working in initial-setup-0.3.62-2.fc29, thanks Martin!
initial-setup-0.3.62-2.fc29, python-simpleline-1.4-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.