update mesa

[darkralts]

Is this a new report?

Yes

System Info

Void 6.3.13_1 x86_64 AuthenticAMD notuptodate rrrmFFFFFF

Package(s) Affected

mesa-23.1.3_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

ValveSoftware/Fossilize#230 (comment)

as you can see here, mesa has some bugs with steam because it is outdated and makes steam almost unusable due to it eating all the ram.

Expected behaviour

the game to open normally and to pre cache vulkan shaders without consuming your ram

Actual behaviour

when you open a game it wil process vulkan shaders and a "fossilize_replay" will start using all your ram until it crashes.

Steps to reproduce

1. open a game on steam with vulkan shaders pre caching enabled
2. wait for it to start caching
3. watch "fossilize_replay" in task manager and check how much ram it is using
4. your pc may crash

[zlice]

mesa hasn't been building 32bit since 23.1.3 afaict https://github.com/void-linux/void-packages/actions/runs/6266633057/job/17018028135?pr=46172

80-prepare-32bit.sh got added end of august i think 337d270

=> mesa-ati-dri-23.1.8_1: running post-install hook: 80-prepare-32bit ...
cp: cannot stat '/destdir//mesa-ati-dri-23.1.8/*': No such file or directory
=> ERROR: mesa-ati-dri-23.1.8_1: post-install_80-prepare-32bit: 'cp -a ${PKGDESTDIR}/* ${destdir32}/' exited with 1
=> ERROR:   in hook() at common/hooks/post-install/80-prepare-32bit.sh:64
=> ERROR:   in run_func() at common/xbps-src/shutils/common.sh:57
=> ERROR:   in run_pkg_hooks() at common/xbps-src/shutils/common.sh:298
=> ERROR:   in main() at common/xbps-src/libexec/xbps-src-doinstall.sh:66

[TeusLollo]

I haven't been able to run the Steam client (Flatpak version) at all since they switched to their new electron-based interface (Not surprising).

Indeed, that interface seems to be producing myriads of problems:

ValveSoftware/steam-for-linux#9630
ValveSoftware/steam-for-linux#9383
ValveSoftware/steam-for-linux#9984
ValveSoftware/steam-for-linux#10001
ValveSoftware/steam-for-linux#8667
ValveSoftware/steam-runtime#403
ValveSoftware/steam-for-linux#9077

Not sure if a flatpak problem, a Void packaging issue, or some dependency missing.
I have tried disabling hardware acceleration, to not avail.

I regularly get a:
amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1) amdgpu: amdgpu_device_initialize failed. libGL error: glx: failed to create dri3 screen libGL error: failed to load driver: radeonsi Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 336 steam-runtime-launcher-service[336]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam" amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1) amdgpu: amdgpu_device_initialize failed. libGL error: glx: failed to create dri3 screen libGL error: failed to load driver: radeonsi

Not sure if related, though. The new client seems to be a bug-ridden mess.

@darkralts Does the Steam client work on your end since they switched to the new electron-based one?

[SpidFightFR]

i tried to update mesa to 23.1.9, the build works but something's messed up with Python3 deps and stuff, now the checks won't pass at all...

[TeusLollo]

i tried to update mesa to 23.1.9, the build works but something's messed up with Python3 deps and stuff, now the checks won't pass at all...

There's been an huge update to python3 and all related packages just today. Could you reattempt and recheck?

[SpidFightFR]

i tried to update mesa to 23.1.9, the build works but something's messed up with Python3 deps and stuff, now the checks won't pass at all...

There's been an huge update to python3 and all related packages just today. Could you reattempt and recheck?

Indeed it's solved now, but now it seems there is a build issue with 23.1.9, x64 builds, but not the other archs and libc. I might need help here...

[SpidFightFR]

If someone wants to help, please come here: #46172

[TeusLollo]

Just wanted to mention that 42207de (mesa-23.2.1_2) did NOT fix issue #46649

Did it fix this?

[SpidFightFR]

Just wanted to mention that 42207de (mesa-23.2.1_2) did NOT fix issue #46649

Did it fix this?

@TeusLollo You seem to have tried both the native and flatpak package. If the issue happens on both, it means it isn't mesa (steam native uses the native mesa package - but flatpak uses the flatpak-provided mesa, independent of void).

I advise you to rather go on the github for steam-for-linux and report an issue there.

[TeusLollo]

Just wanted to mention that 42207de (mesa-23.2.1_2) did NOT fix issue #46649
Did it fix this?

@TeusLollo You seem to have tried both the native and flatpak package. If the issue happens on both, it means it isn't mesa (steam native uses the native mesa package - but flatpak uses the flatpak-provided mesa, independent of void).

I advise you to rather go on the github for steam-for-linux and report an issue there.

You're right, I should also re-test with steam native. I forgot that flatpak packaged its own mesa. Thanks.

[TeusLollo]

@SpidFightFR Indeed, it does work with steam native.
OK, then flatpak does not work still because they did not update their own mesa version, but now Void native, with 42207de (mesa-23.2.1_2) will be fine.

Thanks everyone.