Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2180277 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2023-03-28 05:22 UTC and the last processed comment was #comment-848720
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
I can reproduce this, but I think I'm: FinalBlocker -1 It doesn't really violate the criterion. Logout works, practically speaking - the session ends, and you get back to GDM. You just get a crash notification when you log back in. The crash notification isn't great, but doesn't violate the criterion. I'd probably be: FinalFE +1 though, as this is a polish issue you can observe on first boot after install (so can't be entirely fixed with an update).
FinalBlocker -1 FinalFE +1
FinalFE +1
FinalBlocker +1
I think this criterion applies here: https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#SELinux_and_crash_notifications "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."
Since this is happens at logout, and not at boot, or first login, I don't really see a criteria that applies. Definitely looks bad though.
This leaves a bad impression with the user. If a fix doesn't come quickly this should be changed to blocker.
If a bug is to be a blocker, it needs to violate some release criterion: https://fedoraproject.org/wiki/Fedora_Release_Criteria
AGREED RejectedFinalBlocker AGREED AcceptedFinalFE
Discussed during the 2023-03-27 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as this doesn't violate the release criteria, but it's a polish issue you can run into before updating so we agree it deserves an FE.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-03-27/f38-blocker-review.2023-03-27-16.00.txt
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.