Fedora Account System
Red Hat Associate
Red Hat Customer
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. :)
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.