FinalBlocker -1
FinalFE +1

In case we manage to get updated shim signed, why not pull it in. Due to the issue affecting only small subset of older hardware, I don't think this is blocker material.

I really wish this would get fixed, but I agree the "limited to specific hardware" escape hatch applies.

FinalBlocker -1
FinalFE +1

I don't know how much of a corner case this is, so I rather vote for blocking and them waive the block afterwards if necessary.

FinalBlocker +1

When we first rejected this issue in F37, we only knew about a small selection of affected boards. By my quick count, we now know about more than a dozen boards, and that's just those listed in bugzilla. I haven't scoured the forums, and the reality will be surely a magnitude worse than reported issues. I honestly don't think we can waive it as a niche problem again. The simplest workaround (install F36 and upgrade) is also getting more difficult, as new hardware is introduced and F36 is getting older.

I understand we might not be able to get a new shim before release. But that's not a reason to reject this. Quite the opposite, if this gets waived as a hard-to-fix blocker (which is very likely), it would be an automatic blocker for F39 Beta. And that's the right thing to do, make it rise in priority for the shim team.

FinalBlocker +1

I agree with what Kamil says

FinalBlocker +1

The simplest workaround (install F36 and upgrade) is also getting more difficult, as new hardware is introduced and F36 is getting older.

But, afaik, the new hardware isn't affected, if I am not mistaken? (And if user matches old affected motherboard with eg. new GPU, it automatically falls back to llvmpipe).

I abstain from this vote, as I cannot judge the real impact of this bug.

FinalFE +1

I don't think this would pass the "last blocker at go/no-go" test.

FinalBlocker -1
FinalFE +1

AGREED AcceptedFinalBlocker

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

The decision to classify this bug as an "AcceptedBlocker (Final)" was made as a conditional violation of "All release-blocking images must boot in their supported configurations" when booting in native UEFI mode on affected hardware.

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

The following votes have been closed:

• Accepted FinalBlocker (+3, 0, -3)
  • +1 by geraldosimiao, kparal, bcotton
  • -1 by frantisekz, nielsenb, sgallagh

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