Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2071394 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2022-04-07 18:37 UTC and the last processed comment was #comment-791232
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
I don't think the criterion is violated, the monitors and rendering and everything seems to work fine. You're just switched to gdm, which can be confusing, yes, but a simple login will return you to your existing session, without any data loss. I don't think we can qualify this as a criterion violation, at least not the one cited. Does anyone have a better candidate? For the moment:
FinalBlocker -1
AGREED RejectedFinalBlocker AGREED AcceptedFinalFreezeException
The following votes have been closed:
Please note this is getting more complicated. This affects a) (dis)connecting external displays b) booting and resizing VMs c) switching your monitor off due to session idle d) breaking autologin (which also affects Lives).
Perhaps the last one could be a blocker, if we can reliably reproduce it. But even if this doesn't directly violate the criteria, just the scope of this bug makes it a bit worrying (what else does it affect?) and very noticeable.
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.