-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SteamCMD fails with futex robust_list not initialized by pthreads #976
Comments
I'm encountering a similar issue with SteamCMD on macOS (ARM) using Docker. (I just coincidentally found this thread on Google when looking for a workaround.) The error is: steam@92b587f0f023:~/steamcmd$ ./steamcmd.sh +login anonymous +app_update 376030 +quit
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
Logging directory: '/home/steam/Steam/logs'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1718904263
-- type 'quit' to exit --
Loading Steam API...Fatal error: futex robust_list not initialized by pthreads
./steamcmd.sh: line 76: 75 Segmentation fault $DEBUGGER "$STEAMEXE" "$@"
steam@92b587f0f023:~/steamcmd$ I recall being able to run the image previously, but I'm not certain. Downgrading Docker to version 4.30.0 didn't help. This might be a SteamCMD issue. |
What do you using to emulate x86_64 on Termux? |
box64 I suppose, as it's box86 repo... |
I know, i just thought maybe he's using something like Box64Droid or Box4Droid cuz its little bit difficult to make SteamCMD work on vanilla Box64 in Termux for me, its just not running (trying to run it natively and then nothing else) i dont know how. Sorry for my bad eng. |
Can you update box86 and try again, see if it works better now? |
After updating box86, Im still getting same error as above. |
This issue is still present for me on the latest commit |
I have actually analyzed this error: the issue comes from a missing syscall on the OS. And even if the syscall was supported, steamcmd also expect the |
I got it working with WINE under Box64 |
Guide? Because when im trying to run SteamCMD with wine under box64 im stuck on this :
it stuck on 0% |
so, there is still not any fix for this? can it be fixed by downgrading box86/64 version or any other solution? |
SteamCMD via Termux fails with this error log
Was working perfectly until a recent update, anyone have any ideas?
The text was updated successfully, but these errors were encountered: