Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2437512 ** Information from BlockerBugs App:
The votes have been last counted at 2026-02-27 02:09 UTC and the last processed comment was #comment-1006992
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
If compiz isn't the compositor for any blocking desktop, as stated by @adamwill on the ticket, I don't see how this can be a blocker.
BetaBlocker -1
I agree with the above. This is clearly not BB King, nor even just a BB.
Not a blocker but happy to give it a Freeze Exception.
BetaBlocker -1 BetaFE +1
I think they misunderstood what the blocker tracker bug means. Anyway: BetaBlocker -1
AGREED RejectedBetaBlocker
The following votes have been closed:
If compiz is the compositor for any shipped spin, I'd be fine with +1 FE for this. Is it still used on the MATE spin? Are we still doing the MATE spin?
It seems we are=E2=80=A6=E2=80=A6.. https://fedoraproject.org/spins/mate/
Derek Enz @derekenz:fedora.im
On Tue, Feb 24, 2026 at 2:53=E2=80=AFPM Adam Williamson pagure@pagure.io = wrote:
adamwill added a new comment to an issue you are following: If compiz is the compositor for any shipped spin, I'd be fine with +1 FE for this. Is it still used on the MATE spin? Are we still doing the MATE spin? To reply, visit the link below or just reply to this email https://pagure.io/fedora-qa/blocker-review/issue/2033
adamwill added a new comment to an issue you are following: If compiz is the compositor for any shipped spin, I'd be fine with +1 FE for this. Is it still used on the MATE spin? Are we still doing the MATE spin?
To reply, visit the link below or just reply to this email https://pagure.io/fedora-qa/blocker-review/issue/2033
It's part of the MATE spin still.
BetaFE +1
BetaFE +1 AGREED AcceptedBetaFE
Log in to comment on this ticket.