Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2446745 ** Information from BlockerBugs App:
Commented but haven't voted yet: lruzicka
The votes have been last counted at 2026-03-24 08:11 UTC and the last processed comment was #comment-1008945
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
The Third-Party Repositories dialog in GNOME Initial Setup is broken on F44, clicking "Enable Third-Party Repositories" does nothing. It is a regression since it worked fine on F43. This dialog is an important part of the Fedora Workstation user experience and as such should work correctly in the Final release.
FinalFE +1
This unquestionably violates a final blocker criterion too, but it probably doesn't pass the "I know a blocker when I see/smell it" test, so freeze exception feels right for this one.
This unquestionably violates a final blocker criterion too
It seems we should have an official vote for the blocker status as well, in this case. I'll add the proposal.
FinalBlocker -1
I don't think I've ever voted against a bug that violates a clear and unambiguous blocker criterion before, but this just doesn't seem serious enough that we would actually plausibly block the release over it.
Criterion should be: "If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test."
Can we please accept this as a FinalFE so the Bodhi update can be pushed to stable before F44 Final? Thanks! :)
I'm really struggling with how something presented to the user on initial setup not working isn't being seen as a blocker. Stuff like this not working is how you develop a reputation, arguably one Fedora used to have back in the Core days, and through years of solid releases has finally really started to shake. It's not like a user has to go out of their way to hit this. You can't fix the initial setup experience with an after release update.
FinalBlocker +1 FinalFE +1
AGREED AcceptedFinalFreezeException
@catanzaro Would you vote differently for a blocker if this was discovered 2 months ago? Or do you think the current criterion is too strict and should be weakened? Because if it violates the criterion clearly, and we still don't want to block on it, then it seems we need to do something about it (for example, change the criterion to explicitly list actions that have to work, and don't include third party repos enablement in it).
The following votes have been closed:
I don't feel too strongly about my vote. I think the criterion is generally good and doesn't need to be changed.
AGREED AcceptedFinalBlocker
Discussed at the 2026-03-23 (blocker / freeze exception) review meeting:
This is a violation of "each page or panel of the initial setup utility should withstand a basic functionality test" criterion.
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-23/f44-blocker-review.2026-03-23-16.00.log.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F44 is no longer tracked by BlockerBugs, closing this ticket.