Skip to content
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

Newest Steam update (Feb 29 2024) fails to launch steamwebhelper #3479

Closed
CallumDev opened this issue Mar 1, 2024 · 2 comments · Fixed by #3482
Closed

Newest Steam update (Feb 29 2024) fails to launch steamwebhelper #3479

CallumDev opened this issue Mar 1, 2024 · 2 comments · Fixed by #3482

Comments

@CallumDev
Copy link
Contributor

Tested with commits 0ef72bf (previously working) and 9ae55ff

Steam simply logs:

steamwebhelper.sh[6094]: Starting steamwebhelper under bootstrap sniper steam runtime at /home/cmcging/.local/share/Steam/ubuntu12_64/steam-runtime-sniper

and tries to restart it once a minute or so. The "steamwebhelper, a critical Steam component, is not responding." dialog appears as well.

System: Ubuntu 23.10 on Pi 5

@CallumDev
Copy link
Contributor Author

@Sonicadvance1
Copy link
Member

Looks like this is hitting a new trap inside of steamwebhelper. Trying to figure out what it is doing.

Sonicadvance1 added a commit to Sonicadvance1/FEX that referenced this issue Mar 2, 2024
Fixes FEX-Emu#3479

As of the Steam update on Feb 29 2024, this is no longer necessary and
actually causes steamwebhelper to abort.

Steam has started using SLR to launch steamwebhelper, which already
passes in --no-sandbox. Adding this argument twice seemingly breaks the
application since it starts complaining that it doesn't understand the
argument and closes with a SIGABRT.

With this removed Steam starts working again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants