Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2071259 Information from BlockerBugs App: <img alt="2071259" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2071259" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-04-04 15:31 UTC and the last processed comment was #comment-790299
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
Feels like a dupe of 2054594. Since it's still occurring, I consider it a failure of the "each page or panel of the initial setup utility should withstand a basic functionality test" portion of the First boot experience criteria.
FinalBlocker +1
AGREED AcceptedFinalBlocker
Discussed using the asynchronous bug tracking platform: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"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."
[0] https://qa.fedoraproject.org/blockerbugs/
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.