Hi. I was on testing branch and I’m using nonfree repo (AMD GPU). Today after llvm, llvm-libs and lib32-llvm-libs upgrade from 16.0.6 to 17.0.6-2 I had issues like parts of the screen flickering and errors when trying to open e.g. mpv:
libEGL warning: DRI2: failed to authenticate
libEGL warning: MESA-LOADER: failed to open swrast [...]
^ that and more. So I used manjaro-downgrade to downgrade the 3 above mentioned packages to 16.0.6, after reboot it works fine.
But what do I do now?
AFAIU upgrading will break it again. Do I keep the packages from upgrading until llvm 17.0.6-3 gets released? For now I switched to stable branch but yay still tries to upgrade llvm so I’m guessing it should work but I’m supposed to do something after upgrading. Should I reinstall something…?
My currently installed `mesa` and `llvm` related packages
That is not correct. All branches are also affected by this problem, because there is a lack of sync between non-free mesa and llvm-libs at the same time.
Do not worry, there is a stabil solution.
Switch back to Mesa from a branch of your choice instead of using non-free Mesa
(Optional) you can write your own shell script that checks video codecs what you need. If codecs are missing, you will be notified by your script.
So I waited a few hours and indeed a new set of mesa packages got released to mesa-nonfree, as @mithrial said it would.
I switched back to testing
did the full upgrade (yay -Syuu in terminal)
However, it didn’t work - the issue came back, so I assumed I need unstable after all, as mentioned by @linux-aarhus so once again:
I switched to unstable
did the full upgrade
Now the issue is gone. I switched back to testing to avoid more unstable packages.
I think @Zesko is also right - the main issue is lack of sync between the community and official repos. And yeah, if I was in a pinch, I’d probably go with @leledumbo 's suggestion and removed mesa-nonfree or recompiled as described by @banjo . Fortunately, I wasn’t in a hurry because TBH messing with those things isn’t my forte.
Thank you all for your help and guidance. Now back to Star Citizen.
The original marked solution is completely erroneous and this thread is full of misinformation. Marked the proper answer as the solution, closing and unlisting it before search engines crawl it.