I have tried to install Fedora Silverblue 42 Beta (Release Day Mar 18, 2025) in a VM using GNOME-Boxes. UEFI was enabled. I have confirmed standard options, but with LUKS encryption enabled (probably not relevant). Silverblue 42 Initial Setup hangs when user activates third party repos. If termination of setup is forced, no user account is created and VM must be shutdown forcibly. When third party sources are not enabled, initial setup continues and finishes normally. Reproducible: Always Steps to Reproduce: 1.Download Fedora Silverblue 42 Beta (Release Day Mar 18, 2025) 2.Create a VM in GNOME-Boxes with UEFI from the downloaded ISO file 3.Confirm standard choices in installer, but enable LUKS encryption 4.Reboot, initial setup starts. In step "Third party sources" activate it 5Ini Actual Results: Initial setup hangs up. After forcing termination, no user account is available, VM must be forcibly shutdown. If activation of 3rd party sources is not enabled, setup continues and finishes normally. Expected Results: Initial setup shall not hang up. If "activation of 3rd party sources" is not applicable to Atomic Desktops, this dialog must not be shown.
Created attachment 2084567 [details] Screenshot of failed step
I can reproduce this too with Fedora-Silverblue-ostree-x86_64-42_Beta-1.4.iso, commit 943800e771d11b1fd47bcec36e058cb01f2da2bea836fc9e93b3746249de77eb. To debug this I set a shell before initial-setup with https://github.com/GNOME/gnome-initial-setup/blob/master/DEBUGGING.md#get-a-root-shell-before-initial-setup-is-complete Here's my journald logs in the VM when reproducing the issue https://paste.centos.org/view/raw/b33a6843 I see some polkit/pam errors in there. gnome-initial-setup uses pkexec specifically when you click "Next" in the initial page after toggling the Third-Party repository button. The issue doesn't happen when third-party repos are disabled. That's https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/blob/master/gnome-initial-setup/gis-pkexec.c?ref_type=heads#L29
`pkexec --user root /usr/sbin/fedora-third-party enable` works as expected. gnome-initial-setup works if I go through the installation without enabling third-party repos and then later force re-run gnome-initial-setup by deleting ~/.config/gnome-initial-setup-done and launching again /usr/libexec/gnome-initial-setup This is likely a user/permission/pkexec issue with the first-boot scenario (when there's no real user account created yet).
Looking at the screenshot, it looks like Gnome Initial Setup - reassigning. :)