Bug 2362164 - Silverblue 42: Initial setup hangs with third party repos enabled
Summary: Silverblue 42: Initial setup hangs with third party repos enabled
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-third-party
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-24 19:49 UTC by Mike B.
Modified: 2026-06-08 16:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 16:59:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike B. 2025-04-24 19:49:34 UTC
After a fresh install of a new system, using the Silverblue 42 install ISO, upon going through the initial setup process, after enabling *Third Party Repositories* and pressing *Next*, the app freezes.

Reproducible: Always

Steps to Reproduce:
- Install Silverblue 42 on a bare-metal or VM, using the available ISO image.
- After a successful installation, reboot.
- After reboot, the Initial Setup (`gnome-initial-setup` component) starts. Navigate though the options pages.
- When reaching the *Third Party Repositories* page, select the *Enable* option. Hit *Next*.

Actual Results:
The setup process hangs, and the *"Initial Setup" not responding* message appears, with the *Force Quit/Wait* options. The *Wait* option doesn't help.

Expected Results:
Next page appears, and the Setup process finishes successfully.

Additional Information:
- Workaround: User chooses to *Force Quit*, force reboots and runs the *Initial Setup* without third party repos enabled.
- This issue does not replicate on the initial setup of a *Fedora Workstation 42* fresh install. 
- Used Silverblue ISO: v42-1.1.
- Initially reported here: https://gitlab.com/fedora/ostree/sig/-/issues/74.

Comment 1 Gurney Buchanan 2025-08-11 16:34:23 UTC
I just reproduced this issue today on a new system (Framework Laptop 13) with the current Silverblue 42 ISO!

Comment 2 Timothée Ravier 2025-09-20 16:54:26 UTC
I haven't been able to figure out why this happened so I made https://pagure.io/workstation-ostree-config/pull-request/682 instead.

Comment 3 Fedora Release Engineering 2026-05-06 12:44:12 UTC
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.

Comment 4 Aoife Moloney 2026-06-08 16:59:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.