Closed ndavd closed 2 weeks ago
running through gdb seems it doesn't crash.
$ DEBUGGER=gdb steam
(gdb) run
[...]
(gdb) quit
🤔
running through gdb seems it doesn't crash.
$ DEBUGGER=gdb steam (gdb) run [...] (gdb) quit
🤔
Can confirm, yea. That's very weird, no?
It's because lib32-glibc
2.39-3. Downgrade it to 2.39-2 and steam will not crash any more.
$ sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-2-x86_64.pkg.tar.zst
Hello @jlsalvador, the distro packaging regression should be mentioned to your distro's package maintainers.
Hello @jlsalvador, the distro packaging regression should be mentioned to your distro's package maintainers.
Yes I known; I'm on it (I'm trying to create an issue for Archlinux maintainers, DONE). My message was to help other users with the same problem. Thank you @kisak-valve 👍.
It's because
lib32-glibc
2.39-3. Downgrade it to 2.39-2 and steam will not crash any more.$ sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-2-x86_64.pkg.tar.zst
Bless you, that was a stressful hour. How could you tell?
Added Packaging Issue: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10
and next time, you should create a upstream packaging issue, if you know that downgrading fixes it. It does really not help anyone, if the issue is for you fixed but rolled out to many people.
Added Packaging Issue: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10
and next time, you should create a upstream packaging issue, if you know that downgrading fixes it. It does really not help anyone, if the issue is for you fixed but rolled out to many people.
Thank you @ptr1337 for reporting the issue in their Gitlab. Just for your context, I reported this issue through emailing directly to Frederik Schwan as soon as I known it is a packaging regression. I can not create an Archlinux Gitlab account (because its Gitlab registration is locked); and because of that I was not be able to create this issue in their Gitlab.
Thank you all.
@jlsalvador @ndavd
Frederik is requesting more logs from you, I can not reproduce the issue on my machine. Could you please update to -3 again and provide the maintainer the required logs?
Thanks! https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10#note_182195
Is there anyone affected who doesn't run nvidia drivers?
@freswa I've sent on your @ requested log + coredump (don't have acc on GitLab). I hope it will help.
@jlsalvador @ndavd
Frederik is requesting more logs from you, I can not reproduce the issue on my machine. Could you please update to -3 again and provide the maintainer the required logs?
Thanks! https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10#note_182195
Sure, I don't have an account there, could you share it with him? steam-runtime-system-info.json
@freswa also emailed you my logs even tho I also use nvidia drivers. Hope it helps to find a pattern. (requested an account into gitlab as well)
It's because
lib32-glibc
2.39-3. Downgrade it to 2.39-2 and steam will not crash any more.$ sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-2-x86_64.pkg.tar.zst
Thank you so much! Like DataCpt I am also curious about how you figured that out. I don't see anything about this library in the crash logs.
This happened on my second day using arch. Hours of panic.
This happened on my second day using arch. Hours of panic.
You got really lucky this time,
Please test glibc-2.39-4
Please test
glibc-2.39-4
Works.
Installed via:
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-4-x86_64.pkg.tar.zst
Please test
glibc-2.39-4
.
Can confirm that Steam works again with glibc-2.39-4. Thanks for solving the problem quickly.
You all rock. I was chasing my tail the past hour until I thought to toss my error in google.
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.39-4-x86_64.pkg.tar.zst
Worked like a charm.
Now i can squeeze in a few rounds before bed
Legendary🪙
I think my issue started after I used sudo pacman -Syu
, which makes me wonder whether this is the best way to keep up-to-date the system.
I used this command today and steam didnt open. After I installed glibc-2.39-4
and it is working now.
I think my issue started after I used
sudo pacman -Syu
, which makes me wonder whether this is the best way to keep up-to-date the system. I used this command today and steam didnt open. After I installedglibc-2.39-4
and it is working now.
Just use -Syu. This regression happened due a change in buildflags and arch did miss to not apply this to lib32 packages. Things like this can happen, when doing changes on the buildsystem and updates.
Closing per Arch fix (glibc-2.39-4)
Your system information
multilib/steam 1.0.0.79-1