bwrap: Can't mount tmpfs on /newroot/var/pressure-vessel/ldso: Permission denied with Steam in Snap packaging
#640
Comments
kisak-valve
changed the title
bwrap: Can't mount tmpfs on /newroot/var/pressure-vessel/ldso: Permission denied with Steam in Snap packaging
|
Hello @VolodymyrVi, Dota 2 is currently run inside the Steam Linux Runtime 3.0 (Sniper) container environment. This section tells us that there's some issue with Pressure Vessel setting up that container environment while being inside the Snap packaging, so I've transferred this issue report to the steam-runtime issue tracker for a runtime maintainer to ponder. |
|
Please give https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information a read and share the requested information. |
|
any news? |
Screencast.from.2024-01-10.21-16-05.webm |
|
I was having this exact issue with Dota and some other games. Like OP I use Ubuntu and installed Steam through Snap, and also had the exact same error message in my runtime diagnostics which hints at a problem revolving around snap. I've worked around it by uninstalling Steam from Snap (which also uninstalls all your games by the way) and instead installed steam through the package manager rather than using snap, after downloading dota 2 again it launches fine without any issues. |
|
I took debug log of the issue before I reinstalled steam with the package manager: |
The Vulkan Shaders is processing here; I don't know why it's taking so long. When it's done, I'll check if it worked and let you know. Thank you! |
It works, THANK YOU ! |
|
Steam as a Snap app is not maintained or supported by Valve. Please report any Snap-specific issues to https://github.com/canonical/steam-snap/issues/. It looks as though this is a problem with the Snap app's AppArmor profile: canonical/steam-snap#356 In general, changes in Steam or the Steam Linux Runtime framework (pressure-vessel) are not going to be able to solve Snap AppArmor problems: it is the Snap app and/or snapd that is responsible for allowing what pressure-vessel needs. |
|
this method worked for me canonical/steam-snap#356 (comment) (manjaro linux) |
|
I have the same issue with Counter Strike 2. |
For completeness, this will affect:
when running on Canonical's Snap-packaged variant of Steam. We do not need additional reports of affected games. The recommended way to install Steam on an Ubuntu system is described in the steam-for-linux documentation. The recommended way to install Steam on non-Ubuntu systems is to use it similarly non-sandboxed. If you want privilege separation between Steam and your other programs, my suggestion would be to create a separate, non-admin user account for playing games, and install/run Steam while logged in as that user account. Valve does not support Canonical's Snap-packaged variant of Steam, or Flathub's Flatpak-packaged variant of Steam: from Valve's point of view, both are unofficial. If those work for you, great, but if they don't work as a result of their respective sandbox layers, that's something to take up with their packagers. The Snap-packaged version is particularly fragile, because of the way Snap/AppArmor is designed, and will often stop working when we make internal changes in the Steam Linux Runtime container framework. I have tried to follow this up with its maintainers to encourage them to develop it in ways that are more future-proof. |
Is this something that i can solve myself or do I have to wait for an update or something like that? |
The only long-term solution for the Snap app is to wait for Canonical to release a snapd update with canonical/steam-snap#356 fixed. A temporary workaround is to find the "Steam Linux Runtime 3.0 - sniper" compatibility tool in your Steam library, and switch it to the Another way you could solve this for yourself is to migrate from Canonical's Snap-packaged version of Steam to Valve's recommended way to install Steam. That will require some technical knowledge to migrate your installed games from the Snap installation to the OS-level (.deb) installation, but it has the advantage that it will not be affected by current or future Snap bugs. |
|
Today's The workaround adds additional complexity to the container runtime framework, which is bad for robustness in the long term (for everyone, not just Snap users), so it will be removed in a future release. If snapd is not fixed before that happens, then the Snap app will regress again. |
This workaround was promoted to the stable branch on 2024-02-12.
This particular workaround is no longer valid - as a result of yesterday's releases, the |
Your system information
Steam->Help->System Information) in a gist:Computer Information:
Steam Runtime Diagnostics
Please describe your issue in as much detail as possible:
After the latest update of Dota2, I can't launch the game.
I push the play button, it says running and then stops.
This first occurred yesterday at 20:00 and continues to this day
Laptop Acer Swift SFE16-42
Ubuntu 23.10
AMD Ryzen™ 7 7735U with Radeon™ Graphics × 16
Also, on the forum, I came across messages from other players who can't launch the game on Mac and Ubuntu 22.04
https://steamcommunity.com/app/570/discussions/0/4139437492714011442/
Steps for reproducing this issue:
Please help me
The text was updated successfully, but these errors were encountered: