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: 1954 bytes --]

New comment by TeusLollo on void-packages repository

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

Comment:
> Further segfaults issues are flooding the issues tab, and don't seem related to this specific bug:
> 
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/12275 (Segfault on Nvidia Quadro) https://gitlab.freedesktop.org/mesa/mesa/-/issues/12283 (Segfault with Gnome-Shell on Intel Integrated Graphics)
> 
> With this many segfaults on all available GPU vendors, I would begin to doubt this is a problem limited to Polaris architecture (Though it's probably a multi-bug release due to fundamental ABI changes). I would say it may be safer to just revert for now, and wait for `Mesa` to cook-up a little their next update. As I said before, they're working on the OpenGL 4.6 API, and thus they're bound to have lots of regressions before stabilizing. Besides, I don't think anyone specifically requesting those OpenGL 4.6 API changes expect them to be finalized already.

OK, those issues seem confirmed, and we're already seeing devolopers commenting, and horror screenshoots. Definitively, there's ABI changes that broke support on multiple architectures, and they don't seem intentional, nor Mesa developers mentioned dropping support for any architecture. I changed the title accordingly. 

I will keep the issue open even after a revert-pull (Which is looking more likely now, unless maintainers want to pull from upstream at least 3 fixes), since we'll probably need some extensive testing on whatever `Mesa 24.3.2`+ package will need to be made after Mesa devs actually can cook-up some fixes, doubt they'll be staying long on `Mesa 24.3.1` with all those bugs cropping up. 

I ask mantainers to link this issue to pull request meant to revert/fix those bugs for easier tracking, if possible. 

Anyone else is free to link this issue to Mesa gitlab devs in case they need more info/testing.