I think iâll stick to the downgraded official packages for now, and wait for a fix to drop there. Then weâll have a good idea whether itâs fixed in both environments.
odd, when I went to activate the rpmfusion free repo it said it was already active. I did activate the nonfree one as well. But if the free repo was already active why when I updated in âSoftwareâ did the problem come back.
after adding nonfree rpmfusion I ran âsoftwareâ update and again got the problem again. going to run the dnf command to roll back the mesa update again.
I also have the same problem since the weekend. In my case the issue is only specific to Firefox. I donât have the same problem with Brave or Firefox Nightly. Therefore I assumed that itâs a Firefox problem, but I also noticed that the problem started immediately after the mesa updates.
From what i have learned, the original problem lies in mesa, but it is triggered by something in ffmpeg. So there are multiple ways to circumvent the bug:
Patched mesa
This is the long term fix, but a patched version that was released yesterday appeared to be incomplete. A new patch that fixes the issue was released today for testing, and can hopefully land in the stable repo on friday.
Patched ffmpeg
There are patched ffmpeg packages that donât trigger the bug in mesa, however there are multiple versions of ffmpeg going around:
Official ffmpeg (free) in the stable repo, this is not patched yet afaik
Rpmfusion ffmpeg (nonfree), this one is now patched
And last but not least, some software like Firefox ships itâs own ffmpeg version. The Firefox ffmpeg was patched for Firefox 130 which is slated for August 5. This is probably the version that you also get when you use the Firefox nightlies.
I think mine is fixed too, but it was a pretty big issue. Needed to hard reset my computer a few times. The external display seemed to be a part of the crash.