User creation could be skipped in KDE 43 "initial setup" wizard coupling with anaconda-webui Reproducible: Always Steps to Reproduce: 1. Download Fedora KDE 43 live image 2. Do liveinst 3. in step 5 uncheck "use local account" 4. finish installation and reboot 5. in old anaconda UI "Initial Setup" wizard , just click finish configuration Actual Results: just directly go to login screen (with no user created) after clicking finish configuration Expected Results: Alert user to create account just like "Quit" button in "Initial Setup" : "Are you sure you want to quite the configuration process? You might end up with unusable system if you do" Additional Information: If you use old style anaconda like Fedora KDE 42. you couldn't process installation if no user is created.
I believe this is a bug in initial setup, it should not allow one to skip the user creation at that stage. Attaching the initial setup screenshot.
Created attachment 2105437 [details] initial-setup-user
So what I think is happening there is that with the GTK UI, *if user creation was provided* Anaconda would force the user to create an admin user - set root password or create regular user with admin rights (doing both also works). And if no user creation was provided - on Fedora Workstation - a different tool (Gnome Initial Setup) was used. So following these conditions, not forcing user creation in Initial Setup was so far perhaps not ideal - but also not fatal, as there would be root password set or a sudo level user & both can not only log-in but also create additional users if required. With the new logic in the Web UI we can end up in a configuration where no user that can log in is created & the old expectation thus breaks down. On technical level it should be fairly easy to make the screen mandatory, just note that it is a slight change in behavior. Right now you can for example create a system with only root password being set and no users being created - even if Initial Setup was started, you could skip it. So maybe we should extend the fix - we have a couple options: - detect root password is set & don't enable Initial Setup from Anaconda - detect root password is set & skip Initial Setup startup (will have to check if root password being set can be robustly done on first boot) - detect root password is set & not make the use creation screen mandatory
After team discussion we decided that the solution will be to disallow proceeding from users step in Web UI when neither root or user is configured.
Proposed as a Freeze Exception for 43-beta by Fedora user kkoukiou using the blocker tracking app because: It is currently possible to complete installation in Web UI installer, without setting a root password or creating a user, and then also skip user creation in the initial setup wizard. This results in a system with no usable login accounts, making it completely inaccessible to user. I assume this bug qualifies for a freeze exception because it breaks a critical installer workflow.
(In reply to Katerina Koukiou from comment #4) > After team discussion we decided that the solution will be to disallow > proceeding from users step in Web UI when neither root or user is configured. This would match the GTK UI behavior, sounds OK. However, do you mean you'd implement this for all environments, or just for non-Workstation environments? Because for Workstation, this might go against the intended experience by Workstation WG, and it would be best to consult them before implementing it.
The Workstation hides the accounts screen through a configuration option, https://github.com/rhinstaller/anaconda/blob/main/data/profile.d/fedora-workstation.conf#L28 If the accounts screen is hidden by the Spin / Edition, then expectedly we will not block finishing the installation without user / root configuration.
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1897 , marking accepted FE.
Upstream PR. https://github.com/rhinstaller/anaconda-webui/pull/983
FEDORA-2025-ae64c15f39 (anaconda-43.37-2.fc43 and anaconda-webui-48-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ae64c15f39
FEDORA-2025-ae64c15f39 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ae64c15f39` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ae64c15f39 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ae64c15f39 (anaconda-43.37-2.fc43 and anaconda-webui-48-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
Setting this back to ON_QA for us to confirm the fix in the first Beta candidate, which I've just requested. It should show up in a few hours.
I added the patch in anaconda-webui dist-git commit in https://src.fedoraproject.org/fork/kkoukiou/rpms/anaconda-webui/c/d96d9e985330159e4a90af1a6246f122e6a6b7d7 but I did not realize there is not %autosetup or %autopatch or %patch0. So this will not be applied. Let's move it back to POST since we have a fix, and I will create a proper release after the Beta freeze.
We're doing another candidate, so I'll do a quick build with %autosetup to apply the patches.
agghhh, crap. no. I forgot about this nonsense when trying to build a patched anaconda-webui: + /usr/bin/make install DESTDIR=/builddir/build/BUILD/anaconda-webui-48-build/BUILDROOT 'INSTALL=/usr/bin/install -p' PREFIX=/usr /usr/bin/make package-lock.json && NODE_ENV=production ./build.js make[1]: Entering directory '/builddir/build/BUILD/anaconda-webui-48-build/anaconda-webui' tools/node-modules make_package_lock_json *** Can't update node modules unless running from git I forget how to deal with that, so unless I remember fast, we'll roll without it.
FEDORA-2025-6d0a06bb12 (anaconda-43.39-1.fc43 and anaconda-webui-50-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6d0a06bb12
On Beta RC3, it is still possible to create a KDE session with NO USER at all and it is not that difficult as there is no warning if one attempts to do so. I would say, this has not been fixed!
The fix is not in Beta-1.3.
FEDORA-2025-6d0a06bb12 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6d0a06bb12` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6d0a06bb12 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-6d0a06bb12 (anaconda-43.39-1.fc43 and anaconda-webui-50-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.