Client cannot start - cannot use steam at all
assert_20240430105903_28.dmp.gz
Uploaded latest assert dump file as well
This is the error window I am getting:
steamwebhelper, a critical Steam component, is not responding. The Steam UI will not be usable. Click here for more information.
[...restart options...]
I believe I am having the same problem. I am on Ubuntu 22.04. Steam was working just fine a couple days ago. Then it did an update when I started. And it now will not start steamwebhelper. It also seems to be still trying to install the update when it tries to launch the webhelper. I have tried removing steam, the .steam and .local/share/Steam directories and reinstalling and it still is failing. Let me know what log information you need.
I tried it again. Steam installs stuff, then goes to verify install and starts to unpack Steam Linux Runtime container, then it tries to start steamwebhelper, I suspect it is getting stuck in a loop during the install process.
same happens to me yesterday on fedora 39 after steam update, tried to clean the steam runtime tar.xz and cef .pak files inside steam/ubuntu12_64 and steam/ubuntu12_32 , steam downloaded and extracted them right but still steamwebhelper not responding
From what I can see on NFS filesystems it appears that the steam-runtime-sniper.tar.xz gets extracted properly. Then it goes to start steamwebhelper, but at the same time starts to extract seam-runtime-sniper.tar.xz again. I've looked at the scripts and can't see any reason why it would do this. Running steam-runtime-sniper.sh with correct arguments extracts the file correctly, a second run with same arguments just starts a run of it. So there is something that makes it think it needs to reinstall stuff.
I am in a similar state, though I'm not sure it's exactly the same as OP. Some typical output happens (in the terminal window) and then things just hang. No Steam UI windows appear. There are a few steam-related processes started. I tried a bunch of things, including chasing down a probable meaningless error about dbus-launch, but nothing worked. Eventually, I just rebooted, and then the UI was able to start up. However, after closing steam and reopening after that, it is back to being stuck. I imagine rebooting will fix it again, but, of course, needing to reboot every time before starting Steam is not an acceptable state of affairs.
This only started happening after a recent Steam client update a few days ago.
I am using Gentoo, KDE. I can open a separate issue if requested.
I seem to be getting the same issue on NixOS with the Flatpak version of Steam. My GPU is Radeon 5700 XT, not that it seems to matter.
FWIW, this problem eventually went away for me. I don't know why, but my current hypothesis is that one of the self-updates of the Steam client fixed it.
same issue on Ubuntu 22.04 on WSL (trying to tas a steam game so i can't just run the game on windows)
Nothing extracted yet.
Your system information
steam --versiondoesn't show a version number and I don't see one in the outputPlease describe your issue in as much detail as possible:
Steam is failing to start for me:
But then errors start to creep in:
And then the system opens an error window that says steamwebhelper is not responding and offers to restart steam with a few options, restart the helper, or quit. None of the options get me anywhere.
This started a week ago and I am unable to access Steam on any reasonable basis.
Steps for reproducing this issue:
steam