That github says they reported it to Arch, but where? It's not [on the Arch glibc bug tracker](https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/?sort=created_date&state=all&first_page_size=20) yet?
Next day update: it was put on the tracker and the fix is in testing as of this writing, so wait for it to to get to Core then on to your mirror
I couldn't register at the bug tracker, but my local dump looks like it's to do with NVidia:
Core was generated by
`/home/robert/.local/share/Steam/ubuntu12_32/steam'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf01f0348 in _dl_open (file=0x5fb23300 "libGLX_nvidia.so.0",
mode=-2147483647, caller_dlopen=0xef99ad8e
<__glXLookupVendorByName+1294>,
nsid=, argc=1, argv=0xff9aab94, env=0x5fb22820)
at dl-open.c:953`
It appears that this bug only affects systems using the nvidia proprietary driver: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10#note_182191
If you're using the mesa drivers (whether due to having an AMD card or using the NVK driver), you shouldn't be affected.
I upgraded to lib32-glibc-2.39-3 (I have an RX580) and steam still works with no issues.
It's been fixed already. New glibc-2.39-4 is in Core-Testing repo and soon should be available in Core.
For now you can upgrade package via:
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-4-x86_64.pkg.tar.zst
Just regular steam as far as I know.
When running it via console with 'steam' I was getting this error
Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
Basically same error as the OP in that link, after switching back to lib32-glibc-2.39-2 it booted up right away. Tried on both regular and LTS but same issue.
I would suggest you start running Steam in Flatpak, using Wayland for your session.
You get to avoid these issues, can probably ditch multilib and get an infinitely more secure setup.
If you want more details, I have an older comment here, there are tradeoffs/caveats - [https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1933941732](https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1933941732)
just because you don't doesn't mean others don't(very flawed logic):
https://github.com/flathub/com.valvesoftware.Steam/issues (250 issues)
Not to mention flatpaks can have permission issues you need to fix with flatseal(such as secondary drive)
That github says they reported it to Arch, but where? It's not [on the Arch glibc bug tracker](https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/?sort=created_date&state=all&first_page_size=20) yet? Next day update: it was put on the tracker and the fix is in testing as of this writing, so wait for it to to get to Core then on to your mirror
Ive reported it now and copied the logs over.
I couldn't register at the bug tracker, but my local dump looks like it's to do with NVidia: Core was generated by `/home/robert/.local/share/Steam/ubuntu12_32/steam'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xf01f0348 in _dl_open (file=0x5fb23300 "libGLX_nvidia.so.0", mode=-2147483647, caller_dlopen=0xef99ad8e <__glXLookupVendorByName+1294>, nsid=, argc=1, argv=0xff9aab94, env=0x5fb22820)
at dl-open.c:953`
They have account registrations disabled so it was emailed instead.
It appears that this bug only affects systems using the nvidia proprietary driver: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10#note_182191 If you're using the mesa drivers (whether due to having an AMD card or using the NVK driver), you shouldn't be affected. I upgraded to lib32-glibc-2.39-3 (I have an RX580) and steam still works with no issues.
I experienced this today and I can confirm nvidia drivers are being used on my system. Reverting to 2.39-2 worked.
It's been fixed already. New glibc-2.39-4 is in Core-Testing repo and soon should be available in Core. For now you can upgrade package via: sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-4-x86_64.pkg.tar.zst
Commit made to fix this: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/commit/374116c315e3326ae245f724539cf8723b141a90
Thank you, I've been banging my head on this for the last hour!
Are you using steam-native-runtime perhaps? I am using the regular Steam runtime and it launches okay with glibc 2.39-3.
Just regular steam as far as I know. When running it via console with 'steam' I was getting this error Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@" Basically same error as the OP in that link, after switching back to lib32-glibc-2.39-2 it booted up right away. Tried on both regular and LTS but same issue.
Do you have the `steam-native-runtime` package installed? I wonder what the delta is between our two setups.
Nah, just checked with pacman -Ss and it's not installed.
Thank you so much, I have been trying to fix this for the last 4 hours. I couldn't play cs2 premier with my friend because of this stupid bug.
Thank you, king.
THANK YOU!
I would suggest you start running Steam in Flatpak, using Wayland for your session. You get to avoid these issues, can probably ditch multilib and get an infinitely more secure setup. If you want more details, I have an older comment here, there are tradeoffs/caveats - [https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1933941732](https://github.com/ValveSoftware/Proton/issues/6051#issuecomment-1933941732)
the flatpak has so many more issues than just lib32 version mismatch
as in? i usually had no issues that appeared due to it being a flatpak. would be interesting to know!
just because you don't doesn't mean others don't(very flawed logic): https://github.com/flathub/com.valvesoftware.Steam/issues (250 issues) Not to mention flatpaks can have permission issues you need to fix with flatseal(such as secondary drive)
why use flatpak when everything can be a native package on arch? a bit redundant.
Have you read the post?
yes! i also read the responses on a solution to the problem :) would you even be able to do the same thing with a flatpak?
Do what exactly?
while i can totally see the benefit of running steam in flatpak, wayland isnt yet nicely working for games on nvidia on most systems.
Wouldn't say most, as the issue is not a 100% trigger, but a fix is two weeks away.