Looks promising. Can I take mesa off of hold now and allow it to update too?
I am at a loss here. I keep getting a lighted screen and a moveable mouse cursor, but not a desktop. I have tried updates
- ignoring plasma
- ignoring frameworks
but to no avail. Is mesa still an issue? Maybe it is mesa.
I rolled back to the state it was in before the updates.
I tried installing the new mesa version all by itself. I did not even get a desktop. So, mesa is still a problem.
I’ve moved your two replies from the latest Stable Updates thread to a System Updates topic.
You’re in an unsupported, partial upgrade state by ignoring important packages.
Help us help you:
1 Like
No, not a partial unsupported updated. I am back to square one.
What @ Yochanan said. You are going to have to provide more information.
I installed the related mesa libraries just now. Rebooted successfully. So, the problem lies in the main mesa package, I think.
@deroberts1 you can get the mesa PKGBUILDs from here: Arch Linux / Packaging / Packages / mesa · GitLab, Arch Linux / Packaging / Packages / lib32-mesa · GitLab. Get the for you known working version by browsing the commit history. You can download the needed files via an archive. Then compile them locally via makepkg and ignore the packages we provide. You might need to recompile your local packages time to time when dependency packages changes or libraries got updated.
3 Likes
I have started testing various versions of mesa on my system. I can happily report that version 2.2.1-1 works great. This a bug fix release of 2.2.0 which was a major update. (It also works.)
Note that I am using it as an NVK open source driver, with the vulkan-nouveau package also installed.
Did you mean 24.2.1-1? 
Again…
1 Like
@deroberts1 if this is about plasma acting weird and broken VAAPI functionality since mesa update to 24.3.x, then you will have to stall mesa at 24.2.7-1. not only that llvm-libs 19.x no longer supports older mesa 24.2.x, you will also have to explicitly install llvm18-libs as well
1 Like