Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2133784 ** Information from BlockerBugs App:
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-10-17 19:39 UTC and the last processed comment was #comment-821724
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 according to the cited criterion
We just discovered that this only affects virtual machines. In this case, it's a conditional blocker, and I don't think running apps from Discover in VMs is such an important use case to block our release on it. Changing my vote to:
FinalBlocker -1
Because this affects the default config for VMs, it's still sufficiently blockery in my eyes. But given the current vote tally, I'll throw in a
FinalFE +1
Ok, I'll follow last vote from Ben.
too much of a special condition use case to block the release (especially that you can start the apps from the DE instead of Discover)
FinalBlocker -1 CommonIssue +1
FinalBlocker -1 FinalFE +1
FinalBlocker -1 FinalFE -1
Any change in this space is likely to have a sizeable set of side-effects. I think we're too late in the cycle to accept it. Document it as a common bug, recommend the use of GPU support in the VM and let it be fixed in an update.
It happens only in plasma-wayland sessions, not in x11.
This can be easily worked around.
FinalBlocker -1 FinalFE -1 CommonBugs +1
For me this requirement is already pretty borderline (we kinda waved the graphical package manager criteria through without discussing it in any detail), and if it's this conditional I'm definitely -1.
I'd reserve a vote on FinalFE until I could see what the fix might look like.
AGREED RejectedFinalBlocker
The following votes have been closed:
Easy workaround for the beginning and then fix later.
FinalFE -1 CommonBugs +1
I think it's too much of a niche case to warrant a FE.
With no obvious proposed fix, I'm not comfortable waving this one in.
AGREED RejectedFinalFE
Discussed during the 2022-10-17 blocker review meeting: [0]
The decision to classify this bug as a "RejectedFreezeException (Final)" was made as, while there would be value in fixing this for installs of apps on first boot before updating, it seems too dangerous to risk poking the software installer this late.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-17/f37-blocker-review.2022-10-17-16.01.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.