Dmoz
May 2, 2024, 4:55pm
1
After updating my pc I am no longer able to open steam and it brings this up if I try to open it in the terminal
[organic@Computer ~]$ steam
steam.sh[3288]: Running Steam on endeavouros rolling 64-bit
steam.sh[3288]: STEAM_RUNTIME is enabled automatically
setup.sh[3361]: Steam runtime environment up-to-date!
/home/organic/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh: line 85: steam-runtime-identify-library-abi: command not found
run.sh[3373]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig
steam.sh[3288]: Canât find âsteam-runtime-check-requirementsâ, continuing anyway
tid(3404) burning pthread_key_t == 0 so we never use it
[2024-05-02 11:52:43] Startup - updater built Jan 13 2024 00:51:43
[2024-05-02 11:52:43] Startup - Steam Client launched with: â/home/organic/.local/share/Steam/ubuntu12_32/steamâ
ILocalize::AddFile() failed to load file âpublic/steambootstrapper_english.txtâ.
05/02 11:52:43 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(3404)
crash_20240502115243_2.dmp[3407]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240502115243_2.dmp
/home/organic/.local/share/Steam/steam.sh: line 798: 3404 Segmentation fault (core dumped) â$STEAMROOT/$STEAMEXEPATHâ â$@â
[organic@Computer ~]$ crash_20240502115243_2.dmp[3407]: Finished uploading minidump (out-of-process): success = yes
crash_20240502115243_2.dmp[3407]: response: CrashID=bp-ead199cc-78a1-40e7-b363-e45b22240502
crash_20240502115243_2.dmp[3407]: file ââ/tmp/dumps/crash_20240502115243_2.dmpâ', upload yes: ââCrashID=bp-ead199cc-78a1-40e7-b363-e45b22240502ââ
[organic@Computer ~]$
hereâs a picture of my steam folder bringing it up since a friend said a folder is missing.
1 Like
Dmoz
May 2, 2024, 4:56pm
2
forgot to mention I did move my steamapps drive out of here and I am not referring to that folder
Appears to be an issue with the latest glibc update. I downgraded glibc and lib32-glibc to the previous version and it works again.
Check out this thread and please use code tags when posting the terminal output to help make it readable
BTW Hi and welcome to the forum
1 Like
Dmoz
May 2, 2024, 5:31pm
4
Thanks for the fast reply but I donât know how to downgrade it can you please explain how I can do it
If you havenât cleared the cache folder then it should be easy to downgrade.
Hereâs from documentation.
https://wiki.archlinux.org/title/downgrading_packages
Dmoz
May 2, 2024, 5:50pm
7
Thanks for the quick reply this fixed the issue really appreciate it!
1 Like
I am new to the forum, I was having the same issue and had to timeshift, how will we know when they have fixed the issue with glibc or the steam client?
ddnn
May 3, 2024, 2:47pm
10
According to this bug report, itâs been fixed as of 6 hours ago: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/issues/10
In the future, you can check for this yourself by going to the package on archlinux.org , then click on Bug Reports to the top right. Once it takes you to the page, click âAllâ to see all the bug reports and search for the issue you are having. See the images below for a visual example.
2 Likes
I tried the update again and it still seems to be broken on my end
ddnn
May 3, 2024, 3:34pm
12
Try updating your system fully, then reboot.
Better yet, after you update fully with one of the below commands, please post the output of your terminal.
sudo pacman -Syu
OR
yay
Scratch that. Never mind. The maintainers havenât pushed the update yet. The packageâs last update still shows yesterday.
Another update: You may need to reinstall the packages, meaning both glibc
and lib32-glibc
.
This is based on: https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/commit/374116c315e3326ae245f724539cf8723b141a90
Update: This bug should be fixed now as theyâve pushed a new update a few hours ago after the bug itself was fixed. Now you can fully update your systems.
1 Like
ddnn
May 3, 2024, 10:52pm
14
Youâre welcome, and welcome to the forum!
2 Likes
system
Closed
May 7, 2024, 12:22pm
15
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.