FinalFE +1

This is a definite FE at least for me. There's potentially an argument for it to be a blocker, though it's a bit tenuous.

FinalFE +1

AGREED AcceptedFinalFE

Discussed during the 2023-04-03 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-04-03/f38-blocker-review.2023-04-03-16.01.txt

The following votes have been closed:

• Accepted FinalFreezeException (+2, 0, -0)
  • +1 by adamwill, geraldosimiao

FinalBlocker +1

For the reasons I articulated in the nomination

I agree that this should be a blocker. Either as a failure of the main panel criterion (a failure to start certain applications as expected - with a reasonable speed), or a failure of basic functionality for selected apps, like the default web browser or problem reporter. This only happens on upgraded systems, but we have a criterion that upgraded systems must satisfy the same criteria as clean installs, so it all checks.

FinalBlocker +1

@kparal 's argumment convinced me to the blocker status too:

FinalBlocker +1

Actually, in this case, we don't have to have the fix in a compose, so the correct approach here is probably to vote for a 0Day blocker here, instead of a regular blocker.

0Day +1

0Day +1

0Day +1

Counting the blocker +1s as 0Day +1s - that seems reasonable, since this definitely doesn't need to go on the images, the upgrade scenario is what we're concerned about - this is:

AGREED Accepted0Day

The following votes have been closed:

• Accepted 0Day (+3, 0, -0)
  • +1 by kparal, nb, adamwill

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