The top one is the result of just libsdl2-dev, the bottom one, libsdl2-image-dev
Mesa downgrade issue
Re: Mesa downgrade issue
now do:
Code: Select all
sudo apt-mark hold libgbm-dev libgbm1
Re: Mesa downgrade issue
That got it - thank you. Interestingly, it looks like there are colour issues in sdl2-ttf. No doubt some big endian issue. Will have to investigate that one. Hopefully the answer isn't to update SDL2 
[EDIT] Actually, not just sdl2-TTF, elsewhere too so potentially it's a broader issue.

[EDIT] Actually, not just sdl2-TTF, elsewhere too so potentially it's a broader issue.
Last edited by MartinW on Wed Aug 27, 2025 2:19 pm, edited 1 time in total.
Re: Mesa downgrade issue
Glad it worked for you too.
Re: Mesa downgrade issue
good luck with your big endian problem
Re: Mesa downgrade issue
It's been brought to my attention that YouTube videos don't display in the correct colours either so my suspicion is it's not SDL2, or my code that has the problem.
Re: Mesa downgrade issue
Are the source packages and build parameters used to build the sources available anywhere (general question)?
I built the mesa stuff last night from the master branch as I think looking at some of the bug reports that at least one factor contributing to us needing to hold it back may have been resolved upstream in a version we don't have yet. It didn't work for me but I wasn't sure if I was selecting the right combination of build options / flags / drivers.
It was 3am by that time so I didn't dig deeper yet so forgive me if the source and stuff is obviously available somewhere. It's also a potentially pointless exercise from my point of view. All I can do with my skillset (at the moment at least) is determine if an upcoming version resolves issues. I don't have the knowledge to contribute fixes. At least I don't think I do. Building on the X5040 wasn't too painful. ~1800 source file in 5 to 10 minutes.
I built the mesa stuff last night from the master branch as I think looking at some of the bug reports that at least one factor contributing to us needing to hold it back may have been resolved upstream in a version we don't have yet. It didn't work for me but I wasn't sure if I was selecting the right combination of build options / flags / drivers.
It was 3am by that time so I didn't dig deeper yet so forgive me if the source and stuff is obviously available somewhere. It's also a potentially pointless exercise from my point of view. All I can do with my skillset (at the moment at least) is determine if an upcoming version resolves issues. I don't have the knowledge to contribute fixes. At least I don't think I do. Building on the X5040 wasn't too painful. ~1800 source file in 5 to 10 minutes.