Hello @luorui93, [2025-04-16 10:09:08] dlmopen steamclient.so failed: steamclient.so: cannot open shared object file: No such file or directory looks like a line of interest from your webhelper-linux.txt log.
Hello @luorui93,
[2025-04-16 10:09:08] dlmopen steamclient.so failed: steamclient.so: cannot open shared object file: No such file or directorylooks like a line of interest from your webhelper-linux.txt log.
Thanks for the reply! I didn't pick this error up because when I ran steam on another machine, it had the same error but the client can launch without problem.. So I think this might not be relevant.
The dlmopen steamclient.so failed: steamclient.so: cannot open shared object file: No such file or directory error is indeed a red herring. It's related to a failed attempt by CEF to initialize the Steam API (it either succeeds by trying different paths, or it doesn't actually need it).
Sorry I fat fingered the close button. I see no useful information that would explain why steamwebhelper is crashing on startup, but if I had to guess it's probably a driver issue.
It looks like you have a software mesa implementation available in addition to your NVidia GPU, you could disable or remove that first. Although it does not look like steamwebhelper is trying to pick it up.
Please run a steam-runtime-system-info diagnostic and provide the result. You can trigger this from the command line with the following command: ~/.steam/root/ubuntu12_32/steam-runtime/run.sh -- steam-runtime-system-info
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/11909#issuecomment-2819219776
Thank you for the help! Really appreciate it! Here is the output of the command you provided. In the meantime I'll try to remove the mesa implementation.
After a long time of debugging. It turns out the culprit is the ESET antivirus software. ESET will 'hijack' all socket communications on the localhost, which for some reason causes the webhelper not working. I was diagnosing another network problem with wireshark and found out this problem. After uninstalling ESET, the steam can launch properly.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]steam-logs.tar.gz
Please describe your issue in as much detail as possible:
I'm trying to do a fresh install of steam on my ubuntu 22.04 machine, after installation, running the steam launch would give me the 'steamwebhelper not responding' error.
Searching through the issues, I found several possible solutions but none of them worked.
-vguiand-no-cef-sandbox, no successxdg-desktop-portal-gnome, no success/tmp/dump, no success, cleared nvidia cache, no successI tried to compare my log with another machine running Steam successfully, the only noticeable differences I can make are
and
Steps for reproducing this issue:
steam_latest.debfrom official websiteI've installed steams on many different Ubuntu machines and this is the first time I encountered this problem. If someone could give some direction that would be extremely appreciated.