ValveSoftware / steam-runtime

A runtime environment for Steam applications
Other
1.17k stars 86 forks source link

Sniper runtime pressure-vessel-wrap python3.9 file error #663

Open Dreyns-c opened 2 months ago

Dreyns-c commented 2 months ago

Your system information

Please describe your issue in as much detail as possible:

No games are working, when I launch them they start to launch and suddenly close. By launching steam in a terminal I get the following error message:

pressure-vessel-wrap[20498]: E: Could not create copy "./lib/python3.9/LICENSE.txt" from "/home/vicomte/DATA/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper/sniper_platform_0.20240321.82093/files/./lib/python3.9/LICENSE.txt" into "/home/vicomte/DATA/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-U6V7L2/usr": renameat: Input/output error Uploaded AppInterfaceStats to Steam reaping pid: 21881 -- steam

I tried some of the solution online such as setting sniper and soldier to previous or beta build neither worked I verified the tool files integrity to no avail.

Steps for reproducing this issue:

  1. launch a game
  2. cry
  3. repeat
smcv commented 2 months ago

renameat: Input/output error

"Input/output error" (error code EIO) often indicates a serious problem with your disk or filesystem. Before doing anything else, I would recommend making sure you have backups of any important files, and checking your disk health (e.g. SMART).

smcv commented 2 months ago

The filesystem containing "Steam Linux Runtime 2.0 (soldier)", which is in /home/vicomte/.steam/debian-installation/steamapps/common, seems to be fine.

The problem you are having seems to be specific to the filesystem containing /home/vicomte/DATA/SteamLibrary/steamapps/common, which is where "Steam Linux Runtime 3.0 (sniper)" is installed.

What filesystem is that? Is it perhaps a remote (network) filesystem like NFS or SMB, or a non-Unix filesystem like FAT or NTFS?

Installing the various branches of the Steam Linux Runtime into a fully-featured local Unix filesystem (such as ext4, btrfs or xfs) is recommended.

Dreyns-c commented 2 months ago

Sorry for the late response.

I formatted the disk to ext4, and now everything seems to work.

Thank you for your help and sorry for the useless ticket !

smcv commented 2 months ago

I formatted the disk to ext4, and now everything seems to work.

What was it before? It would be useful to know so that we can document certain filesystems as known-broken.

Dreyns-c commented 2 months ago

I recently switched from windows, it was a NTFS partition.