On Thu, 2022-09-22 at 13:01 -0400, Ben Cotton wrote:
6. mesa —
https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW
totem: nouveau_pushbuf_data(): totem killed by SIGABRT
totem plays ~1 second of video and then crashes. This appears to
happen with all video formats. This appears to be an issue in
multithreading support in the nouveau driver, which is fixed upstream.
The fix is large and may not be suitable for backporting, but would be
available in a mesa-22.3 update.
Well, it's not so much backporting that's the problem. It's just that
it's a large change and nobody seems to be super confident about just
throwing it into F37, whether via a backport or a new mesa release. I'm
really not sure what we should do here. It may honestly be safer to
ship the way we are, with a known bug, and then do mesa as a post-
release update; it's much safer in a way to do something as a post-
release update, because then we at least have a "known not-completely-
broken" version in the release repo, and our release live image is in a
known-not-completely-broken state. We can then let the update sit for
testing until we're relatively confident it's better than the current
state.
If we decide to put the new version in for release then belatedly find
out the new code has significant problems that are worse than video
playback in totem, we're up a much rougher creek.
So, this one seems like a bit of a tough call. It would be a good idea,
I think, to get an update with the new code rolled at least, then
people can try it out and we can start getting an idea whether it has
problems...
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net