-
-
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
Steam installed via install_steam.sh script not working #975
Comments
Are you using the BOX86_LOG=1 variable? if not I would do so as it will give you a more comprehensive log. Enable it by entering |
I wasn't using that, but setting this environment variable doesn't seem to have changed the output. |
I tried tracing which commands and scripts are executed in which way when running the "steam" command, and I found the actual steam binary, which is started in the end. When executing it directly, I get the same error, that the required file is not found. Is that a potential architecture conflict here? Or what might be broken in this case? I read that a similar error happens when trying to run a DOS script in bash, which can be converted, but that's not the case here. |
Apparently the scripts don't run steam with box64. Running the binary with box64 manually does start steam, but it immediately crashes, as steam needs to be online in order to update. How does steam not have an internet connection here? The script seems to be kinda broken. |
steam is a 32bits process, so it will run with box86 (and then, steam will launch steamwebhelper, that is a 64bits process, and needs box64, so will need both to run steam). file no found means that you either lack binfmt integration, or the armhf subsystem entirely Read the COMPILE.md to see how to add armhf subsystem on Debian/Ubuntu type of OS. For anything else, you'll to google it. |
That should be the solution then. I have been warned by apt that binfmt doesn't work inside containers. I gotta do that then. I'll report back to you once I tried it and tell you whether it worked. |
I added the x86_64 version of bash and have also added the environment variable. In the logs I can see that it uses the x86_64 version of bash when running |
I removed all steam files and re-ran the script. Now it updated the steam runtime environment, but it still fails running steam, with the x86_64 bash set up to be used by box64. Here is a part of the log:
|
Does the issue persist if you either:
|
I would have to compile it then. I'm using the prebuilt package for Android. Also, I don't really know how to include those in the flags. I've never really messed with building things this much. |
Can you update and try again, it might work better now. |
What do you mean with both in the same folder? You mean that the binaries run for steam are all in the same folder, or that also an x86 version of bash is located in the same folder? Or even box64 and box86 being located in the same folder? |
Running the steam script with box64 and the BOX64_BASH variable set, after reinstalling steam, and with the latest version of box64, doesn't seem to work either. Still the same error when it's trying to execute the 32-bit steam binary. |
I'm experiencing the same issue. I have created a proot with ubuntu (termux) and I have compiled following the instructions for the snapdragon 888 both box86 and box64 (for a samsung tab s9 ultra). After that I used the installer script in this repo for steam. I'm not sure if everything is setup correctly. I ran
|
I installed Steam via the install_steam.sh script in the root of this repository inside of a proot-distro Debian instance, which was shipped with Termux_XFCE. I made sure that binutils is installed, because the
ar
command has failed to run. Steam is installed, as it seems, and I tried running it with thesteam
andbox64 steam
commands, but I am getting this error, together with the rest of the output (this example is from running it with box64 manually):I looked at some things but couldn't figure out what was going on. Am I doing something wrong or might this be a general issue/bug?
The text was updated successfully, but these errors were encountered: