Steam with symlinks crashing repeatedly in steamwebhelper on startup
#10547
Comments
|
Hello @62832 - your logs report a |
Assuming I was supposed to invoke |
|
If your system is setup to collect crashes (coredumpctl) you could check for steamwebhelper crashes and provide the coredumpctl debug output for some of those? |
|
Since I use a non-systemd based distribution, I do not have |
|
Got the same issue in ubuntu 22. from several issues discussions I tried -cef-disable-gpu, -system-composer but nothing worked. steam.sh[107040]: Running Steam on ubuntu 22.04 64-bit XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf08879c0 and from steamwebhelper log : steamwebhelper.sh[107900]: === jeu. 29 févr. 2024 06:36:29 CET === |
|
I have somewhat the same problem with Debian Testing using a Radeon RX 5700. Should I open a new issue? |
|
tried to launch manually the webhelper : while steam was trying to launch iun another shell. Got this error : Could this be linked to the captive chromium ? |
|
@62832 I had not initially noticed this, and unfortunately you didn't mention it. It looks like there are symlinks in your setup? Could you detail what you are doing with |
|
@TTimo I have similar problem and I have symlinked my ~/.local to another disk, because I ran out of space on my home. Are you saying this kind of symlink is not allowed anymore or is there some fix? |
@TTimo My home partition is on an HDD, whereas I keep Steam installed on a separate NVMe SSD mounted under |
|
We typically fix issues caused by symbolic link setups when we come across them, but that'll always be prone to breaking. We do not recommend this. |
@TTimo I have the same issue without any symlinks. |
TTimo
changed the title
steamwebhelpersteamwebhelper on startup
|
I am having the same issue with or without -cer-disable-gpu - no symlinks in my case - I have 3 game libraries on separate drives though (no symlinks involved, just full paths). Crashing for me every time since the last non-beta update |
|
My issue also had problems with symlinks. Fixed it by removing them since it was only the |
|
(Cross-posted from #10552) As a general piece of advice for anyone experiencing an issue similar to this one, symlinks are not ideal as a mechanism for offloading sections of the filesystem to a different disk, because they are application-visible, and in particular they interfere with container technologies. Mount points and bind-mounts will be less likely to cause strange application behaviour. The reason this became an issue recently is that previously the Steam user interface used an Symbolic links are a particularly frequent problem for container frameworks like the Steam Linux Runtime, because merely bind-mounting If the container framework knows about specific locations that need to exist - for instance There are some target directories that should usually work even though we don't have a special case for the symlink, because we do have a special case for the target: anything below There are also some target directories that we can't ever use for technical reasons, even if the symlink that points to them is on our list. Anything below Anything that is not on either of those lists, for example non-standardized mount points like |
There are several situations that can cause the steamwebhelper not to work. For this particular issue, the only one that is in-scope is if there are symlinks in locations that are important to Steam (some of which are not immediately obvious, like Anyone else who is experiencing the "Steamwebhelper is not responding" dialog, please check the Steam logs for more information (Flatpak users: If your symptoms and logs match symptoms and logs seen by other users, you can subscribe to an existing bug report without adding comments by using the "Notifications" panel. You can help us to solve bugs more quickly by only replying if you have new information. |
According to #10552, this turned out not to be true: the root cause seems to have been |
|
it worked, it was the symlink on .config that I changed now for a mount --bind. |
|
Can confirm. I've swapped out the symlinks I had for |
|
Okay so turns out my crash was same reason due to symlinked running I have ^ This is reposted since I commented in wrong issue. |
|
Changing only ~/.config from symbolic link to bind mount also seems to be enough to get it working. |
For
This will still be true. Bind-mounts are always going to be more reliable at a container boundary than symlinks.
The container runtime framework cannot solve this part, so that would be a request for steamwebhelper or CEF: "should log something useful if it tries and fails to dereference a dangling symlink at |
|
In my case, having just Steam's dirs symlinked works fine. |
This change went out in a Steam release recently (yesterday?) so it should now be fixed. The same change preemptively addresses a list of other locations that could conceivably have the same problem, like The original reporter of this issue, @62832, already said that turning their symlinks into bind-mounts avoided this crash for them, so I think we can consider this particular issue report to be solved. For commenters who are not @62832, if you are still having trouble with Steam crashing during startup, I think we will get the best signal-to-noise ratio (and therefore highest chance that things can be fixed soon) if you can report those issues separately with full details, including any error messages that appear in |
|
Can confirm that this issue has been resolved. I've switched back from bind mounts to symlinks for Shall this be closed as resolved? |
Yes please. |
|
My home dir /home/user is a symlink, is it the same problem like have a symlink on .config? |
Similarly to issues #10431 and #10538 and immediately following installation of the new Steam update today, Steam consistently refuses to start up due to
steamwebhelpercrashing every time. Reinstalling Steam as a whole under its standard location does nothing to fix this either.The text was updated successfully, but these errors were encountered: