pressure-vessel-wrap error: Could not create copy renameat: input/output error

AndreaLiboni commented 6 months ago

Your system information

Steam Runtime Version: 3.0 (sniper)
Distribution (e.g. Ubuntu 18.04): Arch linux
Link to your full system information (Help -> Steam Runtime Diagnostics) in a Gist:
Have you checked for system updates?: No
What compatibility tool are you using?: Proton 5.13+
What versions are listed in steamapps/common/SteamLinuxRuntime_sniper/VERSIONS.txt?

#Name   Version     Runtime Runtime_Version Comment
depot   0.20240307.80401            # Overall version number
pressure-vessel 0.20240306.0    scout       # pressure-vessel-bin.tar.gz
scripts 0.20240306.0            # from steam-runtime-tools
sniper  0.20240307.80401    sniper  0.20240307.80401    # sniper_platform_0.20240307.80401/

Please describe your issue in as much detail as possible:

When trying to launch any games with proton i get this error: pressure-vessel-wrap[3186]: E: Could not create copy "./lib/i386-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders" from "/run/media/andrea/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper/sniper_platform_0.20240307.80401/files/./lib/i386-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders" into "/run/media/andrea/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-AE1BL2/usr": renameat: input/output error

I have a system with a dual boot, and the steam library where the games, proton and the steam-runtime is in separate disk from the steam application. The disk is shared between Windows and Linux and is a ntfs disk. The /etc/fstab where i mount the partition looks like this:

# /dev/nvme1n1p2
UUID=CC5C99515C9936E4 /run/media/andrea ntfs uid=1000,gid=1000,rw,user,exec,umask=000 0 3

Steps for reproducing this issue:

launch any game

Hope to find a solution!

kisak-valve commented 6 months ago

Hello @AndreaLiboni, noted at https://github.com/ValveSoftware/steam-for-linux/blob/master/RelNotes.md#installation, sharing Steam library folders between OSes is not supported and can lead to undefined behavior.

Having written that, it's likely unrelated to your specific issue and we've seen similar before at https://github.com/ValveSoftware/steam-runtime/issues/587#issuecomment-1540095422. The general recommendation is to use a Linux native filesystem with Proton and the Steam Linux Runtime container environment.

AndreaLiboni commented 6 months ago

Thanks for the answer! Moving both Proton and the Steam Linux Runtime to the Linux file system actually fixed the problem, thank you!

ValveSoftware / steam-runtime