#240 rhbz#1924908 Long delay before GNOME Initial Setup runs on first boot, "Oops, something went wrong" screen visible at times
Closed 2 years ago by blockerbot. Opened 3 years ago by blockerbot.

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

Current vote summary

  • Accepted BetaFreezeException (+0, 0, -0)

Commented but haven't voted yet: coremodule, tablepc

The votes have been last counted at 2021-03-15 21:02 UTC and the last processed comment was #comment-721308

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)


AGREED AcceptedBetaFE

Discussed during the 2021-02-22 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as this doesn't prevent anything working in the end, but looks very bad as a first impression.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-02-22/f34-blocker-review.2021-02-22-17.07.txt

The following votes have been closed:

  • Accepted BetaFreezeException (+0, 0, -0)

I think this needs to be promoted to Blocker status. I don't believe we really want this to be the First Impression people get when they install the Beta of F34.

Discussed during the 2021-03-15 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as this isn't a completely clear call, and the fix is verified in Beta, so we will just punt to avoid having to think too hard about it.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-15/f34-blocker-review.2021-03-15-16.00.txt

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

2 years ago

Release F34 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata