Steam (steamwebhelper) crashing on start after recent update #10577
Comments
As I think I mentioned elsewhere, this is only a warning and not a fatal error, but it would be good to look into this in your OS. As documented in https://github.com/ValveSoftware/steam-for-linux/blob/master/README.md, Steam requires 64-bit (x86_64, amd64) and 32-bit (i386, IA32) graphics drivers, so I would normally expect you to have Since you mention Clear Linux: if I remember their filesystem layout correctly, I think that means both |
As I mentioned elsewhere, this is only a warning and not a fatal error, but you can improve startup performance by arranging for the To give you an idea of what this might involve: on Debian, which I'm more familiar with, you would either install the |
|
Unfortunately I don't see any obvious root causes for this crash in the logs. One thing to try is to check whether Another thing to try is to check whether If it isn't either of those, then I've reached the limits of what I can to do debug this, so someone with access to Steam internals will have to take over from here. |
Actually, perhaps we can already rule out that theory, because you quoted Steam successfully uploading crash reports, and I don't think it would have been able to do that if |
|
Just added 32-bit GLX libs, still craches. ls -ald ~/.config ~/.config/cef_user_data
drwx------ 1 inferno inferno 3060 Mar 6 10:09 /home/inferno/.config
drwx------ 1 inferno inferno 46 Jun 24 2022 /home/inferno/.config/cef_user_data |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Hi, I'm hitting the same crash on startup after an update, too. I believe it to be an EGL issue; more information inline. For Valve employees, ticket HT-DHFG-GGBD-85VD has I see the same symptoms as inferrna, but have more logs: Reading through that terminal output, I saw a log for steamwebhelper and it appeared to have an issue initializing EGL. The log for it is in ticket HT-DHFG-GGBD-85VD; apologies that I no longer have it to attach here. glx is fine: and There's a chance this might be a race. Yesterday I managed to get steam to startup by manually running "Lumencraft" from the command line; it seemed to need steam APIs and start the steam client itself, and magically worked. The same trick did not work today, and so I now believe I just got lucky with that startup. Corroborating that theory: today I occasionally ran FWIW, I now have "Enable GPU accelerated rendering in web views" disabled in my settings (turned it off yesterday, after the issues started). The issues continued today so it seems this setting did not have impact. I wonder if steam is sandboxing steamwebhelper but also trying to use EGL, and that sandboxing is preventing access to GL? Just speculation. If it's fruitful, is there a way to tell steamwebhelper to not bother with GPU acceleration? There's an option on this for the main client, but it's not clear that it impacts steamwebhelper. My system: |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Same problem exists on Debian as well. I tested downgrading Mesa to 23.3 from 24.0 to see if there's a difference, no help. This appears always on first start of the Steam. Once you are in Steam client, exit and start it again to fix the situation but that is slow and cumbersome. But since it seems to vary on start timing there is perhaps something in initialization not being fully ready when the "friends" app is starting? (It is always that one that does not work when client has loaded in addition to profile being not loaded correctly.) |
|
Some clarification: in the first start (when crashing) I don't see the "login splash screen" at all. In the second start (after exiting once) the login splash is visible almost immediately and there's no crash. If login didn't work this might explain why profile and friends app are not working either? |
|
Problem reappears after rebooting computer when starting the client takes longest. Logging out and back in does not cause the crash. |
|
Since it always takes a long to appear, it might be a timeout instead of simple crash? |
|
I think I'm also running into a similar issue in (K)Ubuntu 22.04 LTS using the "amdgpu" display driver, I started having this issue after a recent update. But for me it's really inconsistent, I observed it has more tendency to crash in the first launch, if I close Steam using the crash dialog that appears and open again I can eventually get Steam working, sometimes I need to do this process three or four times until steamwebhelper stops crashing. I will try to get logs as soon as I can. I should also mention I am running the entire Steam installation from an spinning hard drive using a symlink to the ".steam" folder inside my home folder that lives in an SSD, I wonder if there is a race condition caused by Steam taking too long to start. EDIT: I forgot to mention I am using the Steam Families Beta but I started having this issue before using it. |
|
My home dir /home/user is a symlink, is it the same problem like have a symlink on .config? |
It might be different problem. I don't see symlink on my system and if it were about symlink it would fail consistently instead of only some times during starting. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@K1ngfish3r, I've opened #10789 to represent your issue where Other users who see that message can follow up on #10789 too. This probably only affects users of Clear Linux. |
|
If you do not see that message, even if the symptom is the same, please do not reply to #10789. The |
|
@tfogal, there is not enough information here to tell whether you are encountering the same issue that was originally reported here by If in doubt, please open a separate issue, with the title as distinctive as possible: closing an issue as a duplicate is much faster and easier than disentangling an issue report that contains multiple root causes.
Sorry, if we are going to make progress on this, we will need to see the actual logs, not just your interpretation of them; and the information about your system that is requested by the issue report template is also important. Note that some error messages involving ANGLE and EGL often appear in These warnings look scary, but seem to be harmlessso you cannot necessarily assume that a particular error message is fatal. |
|
@ipr, there is not enough information here to know what is happening on your specific system, and you have not provided logs or system details beyond "it's Debian".
This sounds similar to #10581. Is your disk or filesystem known to be particularly slow? (My test machines used for Steam Linux Runtime development have a traditional magnetic HDD, not a SSD, and I have not encountered this problem myself.) |
|
@JORGETECH, there is not enough information here to know what is happening on your specific system, and you have not provided logs. If your disk or filesystem is known to be particularly slow, then it might be the same thing as #10581. |
You have not provided any logs or details of your system beyond what I quoted here, so I cannot say what is happening on your particular system. As a general principle to get better robustness, whenever you are offloading things to a different disk, I would recommend using bind-mounts in preference to symlinks. Having said that, the known issue for |
This comment was marked as resolved.
This comment was marked as resolved.
|
With the new beta version steamwebhelper is still crashing on Debian. Yet this is somehow worse that main UI does not start at all when steamwebhelper crashes. Steam beta 1713317598 Client build date 17.4., Web build date 15.4. Kernel 6.8.7, Mesa 23.3.5 Logs from stable version: |
|
One line that does not appear upon successfully starting: This seems to be only in log when crashing. |
Hi @K1ngfish3r, to run from the terminal end get your This will create a file To get the environment from the .desktop file, I'd ask you to copy your .desktop file to a new one, and then edit the command inside the new one (probably by right-clicking and going into a 'properties' or similar). The command is probably something like Once you have the two files of your environments, you could run: and it will show some lines with |
|
In fact, I have to thank @K1ngfish3r because it got me thinking about environments. I have determined that, on my system: works, while: fails. When it works, Attaching logs from these two cases, but they're really not elucidating. Interestingly, Hypothesizing: something is trying to initialize audio, but it's taking much longer than expected and a timeout occurs, causing cascading failures. I do not know why the initialization is taking so long. Note that |
|
@tfogal, please open a separate issue with a title like
It could be audio, or it could be anything else that uses |
|
@ipr:
This seems notable enough to be something that would be useful for a steamwebhelper developer to investigate as a distinct issue. Please open a separate issue with full details and logs, and mention "TypeError: Cannot read properties of undefined (reading 'RegisterForComputerActiveStateChange')" in the title. |
|
Steam updated to 1714854927 assert_20240512135300_30.dmp[261153]: Finished uploading minidump (out-of-process): success = yes
assert_20240512135300_30.dmp[261153]: response: CrashID=bp-feaf08cd-14b7-45f5-80f8-1e6572240512
assert_20240512135300_30.dmp[261153]: file ''/tmp/dumps/assert_20240512135300_30.dmp'', upload yes: ''CrashID=bp-feaf08cd-14b7-45f5-80f8-1e6572240512'' |
|
I got caught in infinite loop during unpacking stage in version After manually removing all Take this info with a big pinch of salt, but if it helps anyone I'd rather post it. |
This is probably a separate issue. There are several things that can cause If you are not @inferrna and you do not have evidence that you're seeing exactly the same crash that @inferrna sees, please open separate issues instead of replying to this one.
A permissions issue is a new thing to have seen there. Please send as much information as you can remember or obtain from logs to a separate issue report, mentioning in the title that it's a permissions issue while unpacking (We cannot fix issues from a description as broad as "permission issue", but if you can provide more information then we might be able to figure out what was going on.) |
|
Fixed for me with 1718305227 |
|
@inferrna wrote:
1718305227 is the current beta version of the Steam client (build date 2024-06-13). Since @inferrna is the original reporter of this issue, we should probably close it now, to avoid attracting replies from other users who are getting a similar symptom for a different reason (cc @kisak-valve). For anyone else who is getting similar symptoms, you could try upgrading to the beta branch. If Steam is not starting at all, you will not be able to switch to the beta through the UI, but you can still upgrade to the beta like this:
(Similarly, if the beta is not working, you can go back to the stable branch by deleting If upgrading to the beta resolves this for you, then maybe you were experiencing the same issue as @inferrna. If so, there is no need to reply here. The same fix should make its way into the stable branch of Steam at some point in the future. For anyone who is still getting similar symptoms after upgrading to beta 1718305227 or later, please open a separate issue instead of replying to this one, with as much information as you can provide (for example any distinctive error messages). A crash similar to the one reported here can happen for several reasons, but each reason needs to be fixed separately: there is no magic bullet that will fix every possible reason for a |
This is now also the stable version of the Steam client, so anyone who was experiencing this issue for the same reasons as @inferrna should now find that the stable version also works. Again, if you are still getting similar symptoms after upgrading to 1718305227 or later, please open a separate issue. |
OS: Clear Linux
System configuration was unchanged since the last successful run of steam.
Normal start
GPU acceleration disabled
Sandboxing disabled
Logs
steam_logs2.zip
also reported in #10549
The text was updated successfully, but these errors were encountered: