Open Botspot opened 10 months ago
I am also suffering from this issue, installed the same way as the OP.
Same issue here, I have even tried going the manual way on the Debian Bullseye (arrch64) version of Raspberry Pi OS. I manually compiled and installed the latest Mesa Vulkan drivers as well. The only thing that sticks out to me from my logs is that vulkan is failing to launch, which could just be user error.
I have tried multiple times and the farthest I have been able to get on a fresh install was the steam update that it does, and then it dies when it tries to load the steam-runtime-launcher-service
I will add my logs below, and I hope it helps bring something to light!
I did some more messing around and I was actually able to get steam to run without issues (other than it just being slow) on Ubuntu 23.10 (aarch64.) From a fresh install, I used piapps to install steam and everything worked as intended. Is this possibly a graphics driver issue with raspberry pi os?
@ptitSeb? Any ideas @ksco?
I don't have issues with steam on my tests machine. I suppose there i a missing dependancies to steamwebhelper somewhere, but no idea wich one. You need to generate logs (using a custom ~/.box64rc
with a correct steamwebhelper
section to find the missing lib.
I don't have issues with steam on my tests machine. I suppose there i a missing dependancies to steamwebhelper somewhere, but no idea wich one. You need to generate logs (using a custom
~/.box64rc
with a correctsteamwebhelper
section to find the missing lib.
Your response was very unclear, but I think this is what I was expected to add to ~/.box64rc:
[steamwebhelper]
BOX64_LOG=2
The output from this is unchanged and it appears that there is no log from the steamwebhelper.
BOX64_PREFER_EMULATED=1 BOX64_EMULATED_LIBS=libmpg123.so.0 /usr/lib/steam/bin_steam.sh -no-cef-sandbox steam://open/minigameslist
steam.sh[250793]: Running Steam on debian 12 64-bit
steam.sh[250793]: STEAM_RUNTIME is enabled by the user
setup.sh[250859]: Steam runtime environment up-to-date!
steam.sh[250793]: Steam client's requirements are satisfied
Box86 with Dynarec v0.3.5 41a8bc0d built on Dec 23 2023 06:24:30
pi@raspberrypi:~ $
@ptitSeb please advise.
It's more tha that. You need to take the section from current /etc/box64.box64rc
and replace the log=0 with log=1:
[steamwebhelper]
BOX64_NOSANDBOX=1
BOX64_INPROCESSGPU=1
BOX64_LOG=1
BOX64_MALLOC_HACK=2
BOX64_DYNAREC_STRONGMEM=1
I understand now. The entire /etc/box64.box64rc file has been copied to ~/.box64rc and I changed BOX64_LOG to 1 as instructed. However, the output still remains unchanged.
pi@raspberrypi:~ $ BOX64_EMULATED_LIBS=libmpg123.so.0 /usr/lib/steam/bin_steam.sh -no-cef-sandbox steam://open/minigameslist
steam.sh[257268]: Running Steam on debian 12 64-bit
steam.sh[257268]: STEAM_RUNTIME is enabled by the user
setup.sh[257335]: Steam runtime environment up-to-date!
steam.sh[257268]: Steam client's requirements are satisfied
Box86 with Dynarec v0.3.5 41a8bc0d built on Dec 23 2023 06:24:30
pi@raspberrypi:~ $
It's like box64 is never called. Don't you have qome qemu-user or fex nstalled that might take precedence to box64 here?
It's like box64 is never called. Don't you have qome qemu-user or fex nstalled that might take precedence to box64 here?
None of those are installed. This is a fairly fresh PiOS Bookworm 64-bit install on Pi5.
@ptitSeb does my original log containing the "buffer overflow detected" error point to anything in particular?
Your initial log doesn't show any trace of box64 running, only box86 seems to be called. Did you reset binfmt integration after installig box64? Did you setup BOX64_BASH to x86_64 version of bash (but it shouldn't mater if you binfmt is present and working).
binfmt is enabled and restarted automatically by pi-apps box64 daily built debs. Binfmt does appear to work as I can run other x64 binaries like Wine and box64 will interpret them correctly.
I have made a logfile for you @ptitSeb with the following commands:
export STEAMOS=1
export STEAM_RUNTIME=1
export DBUS_FATAL_WARNINGS=0
BOX64_LOG=2 BOX64_EMULATED_LIBS=libmpg123.so.0 /usr/lib/steam/bin_steam.sh -no-cef-sandbox steam://open/minigameslist 2>&1 &> ~/Desktop/steam.log
Did you cut the log? because it looks like it start in the middle of running steam-runtime-identify-library-abi
? looks like some buffer overflow. Might be caused be using a mix of native and emulated gtk libs, but I don't see the part were libs are loaded. A LOG=1 should be enough tbh, LOG=2 is overkill for now. Also, is it some beta of steam?
The log is complete and uncut. This is not a beta version of steam and I am not the only person encountering this issue.
A LOG=1 should be enough tbh, LOG=2 is overkill for now.
LOG=1 is completely unhelpful.
This is the contents of steam.log when running the same command as last time but with BOX64_LOG=1:
steam.sh[297630]: Running Steam on debian 12 64-bit
steam.sh[297630]: STEAM_RUNTIME is enabled by the user
setup.sh[297700]: Steam runtime environment up-to-date!
steam.sh[297630]: Steam client's requirements are satisfied
It's more tha that. You need to take the section from current
/etc/box64.box64rc
and replace the log=0 with log=1:[steamwebhelper] BOX64_NOSANDBOX=1 BOX64_INPROCESSGPU=1 BOX64_LOG=1 BOX64_MALLOC_HACK=2 BOX64_DYNAREC_STRONGMEM=1
I added this to my config too. No change like @Botspot is saying. Here's my log if its any help. This is on a fresh install of raspberry pi os.
I did some more messing around and I was actually able to get steam to run without issues (other than it just being slow) on Ubuntu 23.10 (aarch64.) From a fresh install, I used piapps to install steam and everything worked as intended. Is this possibly a graphics driver issue with raspberry pi os?
And again, this seems to only be a issue on raspberry pi os from my testing.
Latest Steam and Box64 and Box86 works for me on Nintendo Switch Ubuntu Jammy. Never saw any issues.
Latest Steam and Box64 and Box86 works for me on Nintendo Switch Ubuntu Jammy. Never saw any issues.
Yeah, it's pretty weird. I wish pi-apps hadn't auto upgraded my packages. Maybe one of those brings up a issue. Then again, I could be completely wrong. 😥
Yeah, it's pretty weird. I wish pi-apps hadn't auto upgraded my packages. Maybe one of those brings up a issue. Then again, I could be completely wrong. 😥
pi-apps does not upgrade packages. This issue it outside of pi-apps control and appears, at this time, to be an issue with some other library (eg: mesa, wayfire, etc) packaged by the developers of piOS or an issue in box64/box86 that only manifests on piOS.
pi-apps does not upgrade packages.
In this case, it does. Steam install-64
below.
I agree with @nanospearing, this really should be using the --only-upgrade flag, or ask permission first.
pi-apps does not upgrade packages.
In this case, it does. Steam
install-64
below. I agree with @nanospearing, this really should be using the --only-upgrade flag, or ask permission first.
Ah that's an oversight. It should be like the wine script and only upgrade box86/box64, yeah.
this above issue as been corrected https://github.com/Botspot/pi-apps/commit/69131933b16587934fcc42da885be7a73308710a
that was the only instance where pi-apps performed an apt upgrade and it has now been corrected
this above issue as been corrected Botspot/pi-apps@6913193
that was the only instance where pi-apps performed an apt upgrade and it has now been corrected
Thanks for fixing that for me! I plan on doing some more testing tonight. I want to see if I can get steam to launch with all of the packages not upgraded. If it does launch, I will deduct which package is the trouble maker, and that might be able to help assist in finding the root issue!
Sadly no change with my testing.
Sadly no change with my testing.
@nanospearing that isn't surprising. If the issue is prompted by a driver problem with MESA then that wouldn't be caught unless you have an an old image where BOTH the armhf and arm64 mesa drivers are already installed. Fresh piOS ARM64 images have the arm64 mesa drivers only, and when the script goes to install the armhf ones, that necessitates that both versions match, meaning the arm64 driver will be updated and armhf driver installed to whatever the latest version is on the apt repositories.
The older versions are still available in the repos, the next steps to rule out driver issues would be for someone to install the older driver versions manually that match the installed arm64 version available on the old image (eg: sudo apt install libegl1:armhf=whateverversionarm64ison libglx-mesa0:armhf=sameasbefore ...
). Obviously all of this has to be done without every apt upgrading
@ptitSeb, have you been able to reproduce this? Is there anything to be done here, or will we have to go tell everyone Steam no longer works under Box64/86?
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam?
Note that I do need export DBUS_FATAL_WARNINGS=0
on my side now to start steam with latest stable version.
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam?
Current version. Could you try testing Steam on your Pi 400? I think this is not a Pi5-specific problem.
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam?
Note that I do need
export DBUS_FATAL_WARNINGS=0
on my side now to start steam with latest stable version.
What OS are you using too? I only ran into issues when using raspi os
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam? Note that I do need
export DBUS_FATAL_WARNINGS=0
on my side now to start steam with latest stable version.What OS are you using too? I only ran into issues when using raspi os
Debian trixie...
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam?
Current version. Could you try testing Steam on your Pi 400? I think this is not a Pi5-specific problem.
I'll try to test that tomorrow.
Debian trixie...
I would try it on Raspberry Pi OS if you're going to be debugging. All other operating systems don't have the issue when I was testing.
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam? Note that I do need
export DBUS_FATAL_WARNINGS=0
on my side now to start steam with latest stable version.What OS are you using too? I only ran into issues when using raspi os
Debian trixie...
I don't reproduce that for now. Steam works fine on my side on my tests machine. But I don't have any Pi5, and didn't tried my PI/400 for some time now. Is that with the current version or a beta of steam?
Current version. Could you try testing Steam on your Pi 400? I think this is not a Pi5-specific problem.
I'll try to test that tomorrow.
ptitSeb, were you able to do any further testing with this?
I tried on my PI/400 some time ago and had no issue. Just Steam eating a lot of memory and needing a swap to be usefull.
But basicaly, Steam works for me.
I am having this same issue where steam will be unable to open.
I an unsure when this issue began to occur, but Steam does not launch using Box64/Box86. This issue was reported by a Pi-Apps user who used Pi-Apps to install Steam. I have confirmed the issue: Steam does not launch successfully.
On first run with no pre-existing config, a number of dialogs appear to download and extract Steam. This seems to succeed. But when running Steam again later, it quickly exits with this output: (Note: /usr/local/bin/steam is a pi-apps custom wrapper script to launch steam)
This output is unhelpful, so I ran steam manually using these commands:
The debug output from this is too long to capture in the terminal, but the ending part seems the most interesting:
My system is Raspberry Pi 5 running the 4k pagesize kernel, PiOS Bookworm 64-bit, wayland
Hoping someone here can look into this and see what can be done to get Steam working again.