Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2180673 ** Information from BlockerBugs App:
Commented but haven't voted yet: mattf
The votes have been last counted at 2023-03-22 23:44 UTC and the last processed comment was #comment-848099
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
Adam summarized it well here: https://bugzilla.redhat.com/show_bug.cgi?id=2180673#c2
FinalBlocker -1 FinalFE -1
This scenario doesn't really make sense for a live image.
I only proposed this because of the second part of the final blocker criterion "Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image." The criterion could be changed to specify that only applies to the liveuser's session. I created the second user in a VM running the live image Fedora-KDE-Live-x86_64-38-20230318.n.0.iso to reproduce the black screen problem on logout with the second user as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2179591
FinalBlocker -1 FinalFE -1 AGREED RejectedFinalBlocker RejectedFinalFE
Sorry for the confusion, Matt. We could amend the criterion, but I think it's probably OK as it is. It gets a bit tricky trying to 'legislate' for every unexpected corner case...
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.