Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2017043
Information from BlockerBugs App:
<img alt="2017043" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2017043" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-02-07 20:54 UTC and the last processed comment was #comment-779727
To learn how to vote, see:
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)
Appears to affect multiple supported hardware configurations, across various applications. Violation of "A working mechanism to create a user account" part of the Expected installed system boot behavior criteria as you cannot create an account through the Gnome Initial Setup without a working keyboard. Or since it impacts multiple apps including Gnome Terminal, violates the Required applications criteria.
Yeah, this looks pretty bad and if one does not expect such behaviour, it can cause much trouble and confusion. Also, it definitely does not look very well.
Discussed during the 2022-02-07 blocker review meeting: 
The decision to classify this bug as an "AcceptedBlocker (Beta)" 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 using a user account created during installation or a 'first boot' utility" (can't log in or create user if you can't type) on affected systems (aarch64 with multi-capability input device).
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.
to comment on this ticket.