Hello @SergeyKasmy, looking at your system information, these lines look important: https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L179 https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L217 https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L229
Your 32 bit mesa render path is broken somehow. Since glxinfo32 works, it's not immediately obvious what's gone wrong here.
https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L299 might be a key detail to focus on. Compare that to https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L566-L575 in the 64 bit section of the extended diagnostics. Is /usr/lib32/libGLX_mesa.so.0.0.0 missing on disk? The lib32-mesa system package might be damaged or incomplete.
https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L299 might be a key detail to focus on. Compare that to https://gist.github.com/SergeyKasmy/58cc2ef3e6bfe8e0ec1770d11e70255e#file-stdin-L566-L575 in the 64 bit section of the extended diagnostics. Is
/usr/lib32/libGLX_mesa.so.0.0.0missing on disk? Thelib32-mesasystem package might be damaged or incomplete.
Both lib32 and normal libraries exist and seem to be in order
$ ls -lh /usr/lib32/libGLX_mesa.so.0.0.0 /usr/lib/libGLX_mesa.so.0.0.0
-rwxr-xr-x 1 root root 447K Sep 28 17:06 /usr/lib/libGLX_mesa.so.0.0.0
-rwxr-xr-x 1 root root 514K Sep 26 11:46 /usr/lib32/libGLX_mesa.so.0.0.0
$ file /usr/lib32/libGLX_mesa.so.0.0.0 /usr/lib/libGLX_mesa.so.0.0.0
/usr/lib32/libGLX_mesa.so.0.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=24e8e70b33e545f015597e62638d820fd597eab9, stripped
/usr/lib/libGLX_mesa.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=9c0c9977572746298ca4824355424b71acef01ac, stripped
I've found an interesting thing but I'm not sure is relevant here, so if it's not, I can create a separate issue.
As I still want to play Steam games, I tried running it via flatpak which worked as intended. Afterwards I wanted to try running it with the mesa-git org.freedesktop.Platform.GL32.mesa-git runtime to check if I would get the CSGO startup fix that landed into mesa recently. After launching steam with env FLATPAK_GL_DRIVERS=mesa-git flatpak run com.valvesoftware.Steam and confirming that it used the newer mesa build, I tried launching CSGO... and nothing happened.
I tried getting the sysinfo from steam with and without mesa-git activated and noticed that it had the same error as I have when running steam natively but only in the Steam Runtime Soldier section. I'm not sure what to think of this but maybe there could've been a regression in mesa recently? Running other games with proton still works
Mesa versions:
Vanilla flatpak: 22.1.7
Native system: 22.2.0
Mesa-git flatpak: 22.3.0-devel
vanilla flatpak steam sysinfo
mesa-git flatpak steam sysinfo
UPD:
downgraded mesa to 22.1.7 on my system but the issue didn't disappear, so it doesn't seem to be an issue with mesa
Hello @SergeyKasmy, looking at the extended diagnostics in those system info gists. The missing libdrm and related lines caught my eye (https://gist.github.com/SergeyKasmy/7f40053886c5c2f0f01701bc612c5b00#file-fp-steam-mesa-git2-txt-L2471) and looking at the list of libraries Steam Linux Runtime - Soldier pulled in at https://gist.github.com/SergeyKasmy/7f40053886c5c2f0f01701bc612c5b00#file-fp-steam-mesa-git2-txt-L1130-L1133, libdrm is coming from some gamescope add-on component. The version of libdrm bundled there is most likely too old to be used with bleeding edge mesa.
Hello @SergeyKasmy, looking at the extended diagnostics in those system info gists. The missing libdrm and related lines caught my eye (https://gist.github.com/SergeyKasmy/7f40053886c5c2f0f01701bc612c5b00#file-fp-steam-mesa-git2-txt-L2471) and looking at the list of libraries Steam Linux Runtime - Soldier pulled in at https://gist.github.com/SergeyKasmy/7f40053886c5c2f0f01701bc612c5b00#file-fp-steam-mesa-git2-txt-L1130-L1133, libdrm is coming from some gamescope add-on component. The version of libdrm bundled there is most likely too old to be used with bleeding edge mesa.
Wow, thanks for looking into this. So it's not the same issue as the original one then? That's a shame, I thought I was onto something.... Now I don't have any more clues why this could be happening. I'll try as much as I can to debug this issue, maybe I'll try to reinstall arch/try different distro/mesa version/etc. I'll update this issue if I find anything. Thanks again
In Debian 12 Bookworm, this error is corrected when the nvidia-driver-libs:i386 package is installed.
Perhaps somewhere in the linux repositories this dependency should appear. Perhaps in a steam-nvidia-libs:i386 metapackage?
Nothing extracted yet.
Your system information
Steps for reproducing this issue:
More info
Clean Steam install just after enabling
multilibrepos (tried both stable and testing). Removed all leftover steam files beforehand withrm -rf ~/.steam* ~/.local/share/Steam.stdout & stderr from steam
Graphics works, output from glx and vulkan infos:
glxinfo
glxinfo32
vulkaninfo
Drivers are all installed and work:
steam and mesa versions
I'm using amdgpu driver with a Radeon R9 270X card, overridden with
radeon.si_support=0 amdgpu.si_support=1cmdline, confirmed that it worksI've seen this often requested, so here's steam sys info from running
~/.steam/steam/ubuntu12_32/steam-runtime/run.sh ~/.steam/steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-system-infoI have no $STEAM_* env vars exported and don't have Arch's
steam-nativepackage installed. I'm running sway/wayland but I have confirmed that it still doesn't work on X with openbox on a new tty.I have checked all similar closed and open issues online and here and have found nothing, so hopefully it's not a duplicate. Flatpak steam works for the most part, VAC doesn't like me running CSGO from inside a container for some reason but I'm still looking into it, it's a completely separate issue though.
Hopefully that's as much info provided as could be needed
Thanks!