Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2459430 ** Information from BlockerBugs App:
Commented but haven't voted yet: lruzicka
The votes have been last counted at 2026-04-20 17:36 UTC and the last processed comment was #comment-1012044
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
FinalBlocker +1
FinalFE -1 FinalBlocker -1
FinalFE +1
FinalBlocker -1 Not sure on FE, I'll wait and see if a fix shows up.
A workaround exists which is turning power save off but the underlying problem is why does power save cause that in the first place
Hardware specific. 5 Mbps is definitely painfully slow by modern standards (assuming reporter meant big M little b, 5 mega bytes per second would be pretty serviceable, 5 milli bits per second would be completely unusable), but fast enough to find workaround online. I'm hesitant to support a FE without any idea what the fix looks like.
FinalBlocker -1 FinalFE -1
Agree. This isn't even blocking hardware.
FinalBlocker -1
AGREED RejectedFinalBlocker
Discussed at the 2026-04-20 (blocker / freeze exception) review meeting:
This is rejected as a non-fatal (but annoying) issue on a single wifi chip is clearly below the threshold. If we blocked Fedora releases on annoying issues on single wifi chips, we'd never release anything. FE status left open as votes are split for now.
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-04-20/f44-blocker-review.2026-04-20-16.00.log.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F44 is no longer tracked by BlockerBugs, closing this ticket.