Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2054594 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill, coremodule
The votes have been last counted at 2022-02-28 21:16 UTC and the last processed comment was #comment-783564
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
Not sure on this one. As described it definitely sounds like a blocker, but Brandon couldn't reproduce it. Might be good to have a few more people try, and get desktop team to look at Lili's crash dump and see if they can see what's going on.
FinalBlocker -1
Feels transient. If something turns out to be broken, or it crashes for other people, I'll definitely hop on the blocker train.
AGREED RejectedFinalBlocker
Discussed during the 2022-02-28 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as we agreed this would be a blocker issue if it were clearly reproducible, but so far other testers have not been able to reproduce it. We can reconsider this decision if we are able to pin the issue down more precisely and it still seems concerning.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.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.