Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1935331 Information from BlockerBugs App: <img alt="1935331" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1935331" />
Commented but haven't voted yet: adamwill
The votes have been last counted at 2021-03-09 18:35 UTC and the last processed comment was #comment-720084
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
This looks awful for affected hardware and it violates the desktop login.
I mean, I'm surprised we're happy just declaring that we block on fingerprint readers now, but hey, apparently!
AGREED AcceptedBetaBlocker
The following votes have been closed:
oh, I see, it's not really about fingerprint login exactly...
Actually, there's a question here. Was this caused by https://bodhi.fedoraproject.org/updates/FEDORA-2021-d2afa6dc55 ? If so, it can't be a blocker, as that update is only in updates-testing.
Per @benzea this is broken in current F34 stable indeed.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F34 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.