Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2458899 ** Information from BlockerBugs App:
The votes have been last counted at 2026-04-17 06:33 UTC and the last processed comment was #comment-1011707
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
FinalBlocker -1
The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver.
FinalBlocker -1 The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver.
Its a firmware issue and nvidia driver has nothing to do with it.
FinalBlocker -1 The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver. FinalBlocker -1 The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver. FinalBlocker -1 The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver.
FinalBlocker -1 The report has little information, it's not clear which bits broke the wifi, it's not clear if the user tested without the proprietary NV driver. Its a firmware issue and nvidia driver has nothing to do with it.
There have been issues in the past when display drivers, and display frequencies have affected wifi, I ask because it's a legitimate possible problem.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F44 is no longer tracked by BlockerBugs, closing this ticket.