-
Notifications
You must be signed in to change notification settings - Fork 174
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
"Steamwebhelper is not responding" shortly followed by "Cannot read properties of undefined (reading 'GetPlayer')" #11079
Comments
For some unknown reason, rebooting seems to have fixed my issue. With the client in the "JS error" state, i still saw steam consuming network resources to update games. |
Not sure if it helps, but I had that error for a few days. Not good for a holiday weekend, but I it seemed to get fixed for me by updating to kernel 6.9.7, it seems a lot of people have had issues in the 6.9 series but I didn't see anything glaring in the changelog to figure anything out. |
Could be due to a recent xwayland regression, see: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1696 with the WIP fix here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1574 |
I'm running MATE, pure xorg, seems a lot better for gaming still. No weird tabbing issues or anything like that. Totally appreciate the suggestion though. |
Still happens to me as well. The exact same error message. |
Same here, Ubuntu 24.04 (Wayland with AMD iGPU). Was working today until my system updated. |
I miss the old days before pressure-vessel where you could either pick to use steams bundled libs, or use the systems libs at your own risk. Some sort of chroot jail or similiar seems less prone to all these error's made by remaking flatpak and then trying to have it figure out mixing host and steam libs on the fly for every combination of system out there. The only thing i've found that helps is to install vmtouch Hope that helps. @schpitz totally blown away that your getting the error on Win10. Welcome to the club |
I have the same issue. It might be related to 9588. Uninstalling any of the However, on my system, Steam always launches correctly after choosing any of the restart options. Only the very first start of the day fails with the described behavior. Operating System: Arch Linux |
It looks like we have a similar error. During the first start-up steam installer during the unpacking process of the "Steam Linux runtime container" an error appears. Clicking restart repeats the error. The only way to get around this is to close the installer window and kill the steam process and then restart it - now steam displays the login window. Quick info: I have collected some logs and core dumps, I am posting them below log running steam installed in terminal: steam-install.txt journallog collected during first steam launching: journal.txt Dumps logs: |
@AngryPenguinPL, please open a separate issue and attach the logs from The logs from |
I just started experiencing this exact issue today. I was playing this morning without issue, turned off my PC and then came back to my PC just now and Steam now won't boot. |
Same here, been like this a few days now. I get a window with the steam logo in a spinning wheel never completing. |
Got this today attempting to start steam. I killed steam client webhelper and attempted to restart and am still getting the error after it spins for a bit. Any workaround for this? |
Welcome to the party, been dealing with this since January. Seems related mainly to pressure-vessel not working for anything but ext4. The only workaround that's currently working for me is make a zram/ext4 at ~/.local/share/Steam/ubuntu12_64 |
My fix was to just uninstall the flatpak version and install the deb |
it somehow works on gnome wayland but not for xorg. |
Your system information
Startup - updater built Jun 20 2024 17:13:49
)Please describe your issue in as much detail as possible:
Issue created after seeing multiple similar reports in #10431, but no NFS/bindmount circumstances are present on my system.
None of the restart options seem to have any effect (not even seeing steam restart at all).
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: