-
Notifications
You must be signed in to change notification settings - Fork 69
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
Steam flatpak crash on startup: Error "steamwebhelper is not responding". (Last Ubuntu apparmor upgrade issue). FIXED #1318
Comments
Thanks, I just wanted to open exactly the same issue, and I was wondering why no one encountered it already. If I look into the logs under Log:
Important part:
It seems that a library is missing in the flatpak, that is used by the latest nvidia driver? Just my guess. Ubuntu 24.04 LTS Btw, running Steam natively without flatpak works on my system. |
Same here. Worked fine yesterday. Only thing I've done since then is Ubuntu 24.04 LTS |
Thanks for response too
Its maybe really missed some X11 library in flatpak Steam repo, but I am on AMD GPU and CPU, so its not problem in |
Ah so it's not only nvidia related :D But I still guess it's because |
If you will startup workable Steam with console feature you will be surprised how many erros its throwing, but working. But this time its not working) |
srt-logger[24324]: Log opened 2024-07-12 11:09:40+0200 Anyone know how long does it take for these issues to be fixed. I was planning on having a nice relaxing weekend gaming. |
Idk. But I now temporary using native Steam for Linux, and its works |
Having the same issue since yesterday. Workarounds are to either use the native Steam client or to downgrade Steam client and keep using the flatpak version (see ValveSoftware/steam-for-linux#11006 (comment)). I am using NVIDIA drivers 550.90.07 |
I also have the same issue on Ubuntu 24.04, 6.8.0-38-generic, with nvidia driver 550.90.07 on a RTX 3080 |
I also have the same issue. Steam was working fine yesterday until today. Ubuntu 24.04, 6.8.0-38-generic, ryzen 2700x, rx 5700. |
Its temporaly thing how to repaire Steam flatpak:
flatpak run com.valvesoftware.Steam -forcesteamupdate -forcepackagedownload -overridepackageurl https://web.archive.org/web/20240210115543if_/http://media.steampowered.com/client -exitsteam and add config for Steam, that it cant be self-upgraded by himself (remember to delete it in future when issue will be gone) for me its:
|
reporting same issue from same time, roughly 2 days ago, as someone else mentioned its nothing nvidia related as i also have an amd gpu and cpu setup, tried all the usual reported methods and it still gives the steamwebhelper error on launch, uninstalled the whole thing and reinstalled with same error. the log files in my case show nothing as they arent generated before it all hangs/crashes. The only useful output i do get when launching via terminal is this output:
nothing else in my terminal output really stands out as a possible error, Webxon's solution is working for me so far but would be nice to know whats gone wrong and how to fix properly. The normal valve deb version works without issue, just the flatpak version is having issues. AMD Ryzen 5 5600G |
Here's what the linkat error looks like under strace:
In another terminal, run
and look for the pressure-vessel pid in an error that looks like:
Inside
Using intel graphics by the way. Thinking the screen recording beta might have broken things, but -clearbeta didn't help. |
@smcv Any idea what might have changed recently? Something in a steam runtime? |
when i launch via terminal my steam briefly lock up at that pressurevessel output you mentioned then after a delay everything fails and all output after is about dump files, i get this which is slightly different to yours.
also
|
If I need to switch from Flatpak Steam to native Steam, how do I not lose all my settings, games, and my game's settings and saves please? |
Something like this:
Before you ever run Steam or its installer. |
...
Inspired by this strace output I've spent some time looking into why creation of the symbolic link is failing. The linkat-error seems to be caused by the recent apparmor-upgrade in Ubuntu 24.04. An additional bwrap-profile was added in the new version. After hitting the "E: linkat: ..."-error the following log-messages have been generated by the kernel (journalctl -k):
WorkaroundSince I don't speak apparmor all that well I ended up removing said profile and restarting the computer to make sure the change is picked up:
Fix?Someone slightly more security-concious should probably look into how to modify the bwrap-profile :) UPDATED: The problem seems to already have been reported to Ubuntu, ref. LP: 2072811. |
Thank you @lothor for finding the cause! I can confirm that
Allows Flatpak Steam to work again. This persists across reboots. |
Reported here in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811 |
aa-disable doesn´t work on my ubuntu 24.04 for some reason. You can use this to disable it instead :
If you want to re-enable it:
I got the instructions from : https://ubuntu.com/server/docs/apparmor |
Please could someone with appropriate permissions retitle this to mention Ubuntu in its title, or close it as "not our bug"? It looks as though this is a regression caused by an Ubuntu stable update (SRU), and is not anything that can be solved by Flatpak or by this particular app. https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811 is the place to look for a solution. |
@webxon 's solution worked for me. |
Hi, there! Yes! Confirm, its Ubuntu issue. I just remember that day, and I am 100% remeber that there are in upgrade list were apparmor application. So its 99% apparmor upgrade. (I will rename ticket) I can confirm next solution for Ubuntu: command
thats all, now I can restart my PC and I dont need to rewrite commands again after restarts. If somebody have used my solution what I have been wrote before, you need now to upgrade Steam to latest version, you dont need anymore version from february, fix:
p.s. remember, if in future apparmor will be upgraded by Ubuntu Devs, this issue may be back, and you'll should repeat this steaps until this apparmor' issue will be fixed |
FYI, the fix has now been released to the Ubuntu repos as part of the apparmor package. Just I think this issue can be closed now. |
I can confirm the fix for Ubuntu 24.04 has been published to the Repos, and after installation, Steam is now able to work properly. On my system, I needed to run a These are the versions of the packages which are working for me per apt. apparmor/noble-updates,now 4.0.1really4.0.0-beta3-0ubuntu0.1 amd64 [installed,automatic] |
I get this on NixOS with the latest Flatpak. Will open another bug report, but I just thought I'd mention it. Ref: #1347. |
I'm pretty sure you don't get this issue, which was Ubuntu-specific and caused by AppArmor. Instead, I think you are getting the same symptom for a different reason. Unfortunately, there are lots of reasons why |
OK - apologies for bringing it up here. |
Yesterday I have running Steam fine, but when I have trying it to startup after few hours its throw me error: "steamwebhelper is not responding".
I have tried, but nothing help:
Error (console):
INFO:root:https://github.com/flathub/com.valvesoftware.Steam/wiki
INFO:root:Will set XDG dirs prefix to /home/user/.var/app/com.valvesoftware.Steam
DEBUG:root:Checking input devices permissions
DEBUG:root:Addding /usr/lib/extensions/vulkan/gamescope/bin to PATH
DEBUG:root:Addding /usr/lib/extensions/vulkan/MangoHud/bin to PATH
steam.sh[2]: Running Steam on org.freedesktop.platform 23.08 64-bit
steam.sh[2]: STEAM_RUNTIME is enabled automatically
setup.sh[75]: Steam runtime environment up-to-date!
steam.sh[2]: Steam client's requirements are satisfied
[2024-07-11 16:19:57] Startup - updater built Jun 20 2024 17:13:49
[2024-07-11 16:19:57] Startup - Steam Client launched with: '/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened' '-no-cef-sandbox'
07/11 16:19:57 minidumps folder is set to /tmp/dumps
07/11 16:19:57 Init: Installing breakpad exception handler for appid(steam)/version(1718904662)/tid(135)
[2024-07-11 16:19:57] Loading cached metrics from disk (/home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/package/steam_client_metrics.bin)
[2024-07-11 16:19:57] Using the following download hosts for Public, Realm steamglobal
[2024-07-11 16:19:57] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-07-11 16:19:57] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-07-11 16:19:57] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-07-11 16:19:57] Verifying installation...
[2024-07-11 16:19:58] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/user/.var/app/com.valvesoftware.Steam/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xed0058f0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xed0041c0
CAppInfoCacheReadFromDiskThread took 71 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 247
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
OS: Ubuntu
before about 1 year all were fine
Have anyone same issue, or know how to fix it?
The text was updated successfully, but these errors were encountered: