Re: Mesa 24.3.1 Update Causing Segmentation Faults On Several-Vendors GPU Architectures

[TeusLollo <TeusLollo@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/53434#issuecomment-2563997175

Comment:
> So I suspect the problem is with the recent mesa upgrade 24.2.8_2. I tried downgrading my mesa but there are so many confusing dependencies that it's very difficult.

Do this:

`sudo xbps-install -Syu xtools`
`ls  /var/cache/xbps/ | grep "mesa"`
`sudo xdowngrade /var/cache/xbps/mesa-(whatever1) /var/cache/xbps/mesa-(whatever2) /var/cache/xbps/mesa-(whatever3)...`

Basically, after you have ensured to have `xtools` on your machine (Which you need to use `xdowngrade`), you use `ls` to list all your `mesa` packages currently in `/var/cache/xbps` (Remember that `xbps` does not provide online downgrades unless it's done by upstream, you physically require obsolete packages in your cache for them to be downgraded), and then you list them after `xdowngrade` to downgrade each and everyone of them. There are safety measures in place, thus, if you happen to attempt to only downgrade some, `xdowngrade` will throw you an error and tell you what's missing, it's relatively safe. 

Obviously, if you already cleared your cache, you won't have any obsolete packages in your cache, and thus this method will be unavailable. 

The manual entry here: https://docs.voidlinux.org/xbps/advanced-usage.html

It may not be related, though, AMD has an history of hard freezes on multiple occasions, although, you never know if a segmentation fault in a wayland-based WM could actually trigger a display freeze. 

As for me, I may be able to test this in a few days, because, you know, end of the year with family and stuff, and it's gonna take a while do compile, install, and perform broad tests, assuming it all goes well.