Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2264946 ** Information from BlockerBugs App:
The votes have been last counted at 2024-02-26 16:37 UTC and the last processed comment was #comment-897987
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
BetaBlocker +1 BetaFE +1
If one can continue with the GIS process, and start using the system, I don't think this is a blocker. The reporter said at the ticket: "...until you have managed to get into the system when the gnome control centre allows you to correct it."
Anyway, an anoying bug, and terrible user experience for sure, but for beta I vote only a FE.
BetaFE +1 BetaBlocker -1
Yeah, I don't think the connection not working blocks g-i-s. Assuming it doesn't:
BetaBlocker -1 BetaFE +1
BetaBlocker -1
I just confirmed you can either select "Skip" after entering a wrong password (after which it will pop up a modal later letting you know it failed to connect, giving you another chance), or if you wait it will pop up a modal (same modal as above) giving you a chance to cancel connecting, or enter a new password.
The most user friendly implementation? Debatable, but not blocker material.
AGREED RejectedBetaBlocker AGREED AcceptedBetaFE
This doesn't violate Fedora release criteria, but would obviously be a nice thing to have fixed and improved, so rejecting as a blocker and accepting as a freeze exception.
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.