Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2179998 Information from BlockerBugs App: <img alt="2179998" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2179998" />
Commented but haven't voted yet: kparal
The votes have been last counted at 2023-03-23 14:48 UTC and the last processed comment was #comment-848160
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
As I said when proposing, users expect to be able to input their passwords or choose their login as soon as the login screen shows itself. Wait for more 15 to 30 seconds on a freezed screen doesnt stand for a good UX quality standard.
FinalBlocker +1
clearly not ready for release. FinalBlocker +1
For me, the delay is short enough (a few seconds) to not be considered a blocker. 15 or 30 seconds would be different. So I guess we'll need to make some guess about how many users are likely to be so severely affected.
Fix tested and confirmed. I think this ticket will be automaticaly closed today, as soon the update get to stable.
I think this ticket will be automaticaly closed today, as soon the update get to stable.
Bugzilla will get closed, and this ticket will disappear from https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist
Excellent, job done :)
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.