Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2069164 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2022-03-28 19:36 UTC and the last processed comment was #comment-788004
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
I think I'm closer to +1 blocker especially given the fact that the accessibility menu is present by default on the login screen. If we disregarded that, I'd have no clear opinion on this.
AGREED AcceptedFinalBlocker
Discussed during the 2022-03-28 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop", in cases where use of the on-screen keyboard is necessary due to lack of a physical keyboard, or accessibility requirements.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-28/f36-blocker-review.2022-03-28-16.00.txt
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.
Log in to comment on this ticket.