FinalBlocker +1

I'm not sure about this, I'm myself can't repreoduce this error the times I started a VM with F41 Workstation.

FinalBlocker 0

I don't think I've seen this. Does it happen every boot, or only initial boot?

I feel like if people are talking about it on Mastodon / Discourse it's probably somewhat common.

FinalBlocker 0

FinalBlocker +1

Discussed during the 2024-10-07 blocker review meeting [1]:

The impact of this seems fairly muted and it seems like everyone but kamil struggles to reproduce it. however, we'll punt to allow for more testing on more hardware.

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-10-07/f41-blocker-review.2024-10-07-16.00.log.html

So apparently it will happen on VMs using the "utc" clock offset (virt-manager default), with more than one CPU configured.

I could see this being a violation of the guest on current stable release criteria, but you could also argue it "works", it's just a little klunky at first.

FinalBlocker 0

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

Discussed at a blocker review meeting [1], agreed on the following:

AcceptedFreezeException (Final), punt (delay decision) on blocker status - this is still a tough one to call and the voting is split. Some people who voted in the issue didn't provide rationale and weren't at the meeting for discussion. for now we will punt on it, and if we're otherwise in a position to do an RC this week, we'll build one without a fix for this (unless it gets fixed) and discuss it again at the go/no-go meeting. It is accepted as an FE so we can get a fix in if one shows up

[1] https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-10-14/

AGREED AcceptedFinalFreezeException

The following votes have been closed:

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

FinalBlocker +1

FinalBlocker +1

As much as I want this to be a blocker, I'm still not really convinced there's a criteria it violates. It's annoying for sure, but only the once (and even then, not if you use Boxes).

Plus it looks like a fix is in the pipeline and it already has a FE.

So, a probably pointless, but in my opinion principled...

FinalBlocker -1

FinalBlocker +1

in case anyone's wondering why this wasn't accepted yet - we've also been discussing it in blocker review meetings, where the voting has been more split, so I've been kinda letting it ride for a final decision at go/no-go. we do have a potential fix for it now, also, but it needs some review from a CUPS expert...

Discussed during the 2024-10-21 blocker review meeting [1]:

Voting on this is at +8 / -7, so it's undecided. as it's an accepted FE and we have a probably-good fix for it, we're expecting to pull that fix in and make this go away that way.

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-10-21/f41-blocker-review.2024-10-21-16.00.log.html

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