Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1861700
Information from BlockerBugs App:
<img alt="1861700" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1861700" />
Commented but haven't voted yet: kparal, coremodule, tablepc
The votes have been last counted at 2020-10-20 08:30 UTC and the last processed comment was #comment-696994
To learn how to vote, see:
AGREED AcceptedBetaBlocker See bug for more info
The following votes have been closed:
Discussed during the 2020-09-24 Fedora 33 Go/No-Go meeting: 
The decision to waive this bug's existing classification as an "AcceptedBlocker (Beta)" in the Go/No-Go decision was made under the "Difficult to fix blocker bugs" exception due to the difficulty in isolating the cause.
If a blocker is waived according to an exception rule, it's moved to the very next milestone per policy. Setting as a Final blocker.
I had finished the standard tests and my as deployed tests on RC1.3 of Workstation with Gnome on my bare metal test system. Then, just for grins, I tried this with the procedure in the bug report. I didn't count but I was able to log in and out between user1 and user2 at least a dozen times with no problem. I know this was reported against KDE, but I thought this might be useful data.
@tablepc Yes, we know it works fine for GNOME. All debugging info should go to the bugzilla, this ticket is just for blocker discussion, thanks.
Discussed during the 2020-10-19 blocker review meeting: 
The decision to waive this bugs classification as an "AcceptedBlocker (F33 Final) and instead classify it as an "AcceptedBlocker (F34 Beta)" and an "AcceptedFreezeException (F33 Final)" was made under the "Difficult to fix blocker bugs" proviso at https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases. We have tried multiple approaches to fix this bug and it's not going away, we are not confident that we'll be able to produce a clear fix any time soon. Tt will be made an F34 Beta blocker instead.
ADMIN NOTE: we need a provision to add a bugs status to a future milestone.
The F34 followup discussion is available in #184.
Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
to comment on this ticket.