#1064 [gnome-shell] reboot/poweroff/logout from GNOME are 60 seconds delayed without 3D acceleration | rhbz#2174753
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2174753 **
Information from BlockerBugs App:
2174753

Current vote summary

Commented but haven't voted yet: bittin

The votes have been last counted at 2023-03-06 15:33 UTC and the last processed comment was #comment-845079

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

I don't understand what criterion this violates (and I haven't seen this on bare metal).

The criterion is cited in https://bugzilla.redhat.com/show_bug.cgi?id=2174753#c3 . If you hit log out/reboot/poweroff and nothing happens, clearly it's not working as expected. If this is just happening in VMs, we could consider blocking Final instead of Beta (no hard opinion here).

I'm adding a FinalBlocker proposal, since @frantisekz and @lruzicka claim their bare metals are not affected.

FinalBlocker +1
BetaBlocker 0

Please note this is going to complicate Beta testing and test days quite a lot, though. And especially annoying is the fact that the user doesn't know about the delay. I'm not sure if I would wait for a whole minute (not knowing about the threshold) when trying to log out, or would kill the VM sooner instead.

While I can reproduce this issue in a VM, it can be easily worked around using the poweroff, reboot, or systemctl reboot -i commands, so I believe that Beta testing will not be hindered much by this. Therefore

BetaBlocker -1
BetaFreezeException +1
FinalBlocker +1

It does seem like a pain, but I'm not sure it quite reaches blocker status for me, at least for Beta.

BetaBlocker 0
BetaFE +1
FinalBlocker +1

BetaBlocker 0
BetaFE +1
FinalBlocker +1

Yeah, it's annoying, but it doesn't really need to block the Beta release.

BetaBlocker -1
BetaFE +1

AGREED AcceptedBetaFE

The following votes have been closed:

BetaBlocker -1
FinalBlocker +1

BetaBlocker -1
FinalBlocker +1

AGREED RejectedBetaBlocker AcceptedFinalBlocker

The following votes have been closed:

i had this problem aswell today, so i am also affected

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.

Metadata