steam-for-linux icon indicating copy to clipboard operation
steam-for-linux copied to clipboard

Source Games refuses to install with "corrupted update files"

Open Zircon777 opened this issue 3 years ago • 2 comments

System information: °Artix Linux x86_64 °Kernel 5.18.12-artix1-1 °Btrfs filesystem with goo free space °More detailed information: https://gist.github.com/Zircon777/10f1355b2510c5c75a336400e5f24d29

After 21th of June i believe, whoever i tried to open tf2 it required an update and since them the game is stuck with corrupted update files This may look like a common issue, so i tried all the suggested fixes:

°Deleting all steam cache, and not only the "clear download cache" option °Changing download region °Using the steam beta client °Repairing steam library folder, and making sure it has the right permisions, my user is currently part of these groups in my system: log games network scanner power users video storage optical lp kvm input disk audio wheel autologin zircon °Installing the game in an ext4 partition

I went as far as creating an fresh debian linux install using ext4, the issue persisted, the smart status of my drive is "healthy" This issue only happens with TF2, 2 other games in my library had this issue but they got fixed by cleaning cache, after that, only tf2 remained and downloading other games of the same size were flawless, so i conclude it's something specific with tf2. Looking at the steam terminal output i got this:

flock LOCK_EX request but file is not opened for writing, ignoring: /home/zircon/.local/share/Steam/steamapps/downloading/440/tf/media/mvm_intro.bik
flock LOCK_EX request but file is not opened for writing, ignoring: /home/zircon/.local/share/Steam/steamapps/downloading/440/tf/media/pl_badwater.bik
flock LOCK_EX request but file is not opened for writing, ignoring: /home/zircon/.local/share/Steam/steamapps/downloading/440/tf/media/pl_goldrush.bik

With ALL the game assets,

I am trying to solve this problem for weeks any help would be appreciated 🙏

UPDATE: Out of nowhere all source based games are failing with the same issue

Zircon777 avatar Jul 17 '22 16:07 Zircon777

Hello @Zircon777, the download and update of game files is handled by the Steam client, not Team Fortress 2, so I've transferred this issue report to the steam-for-linux issue tracker.

kisak-valve avatar Jul 17 '22 16:07 kisak-valve

Hello @Zircon777 - the flock warning is a red herring. There may be more information about the problem in your content_log.txt file - unfortunately these errors can have a lot of different causes.

TTimo avatar Jul 18 '22 13:07 TTimo

Just stopping by as I searched for open issues about BtrFS. I found out that Steam or better the Steam Runtimes have multiple issues with a Library located on a BtrFS formatted drive.

Recently I moved to MicroOS which uses BtrFS by default for the system and the home folder and user apps are running via flatpak.

Therefore I ran Steam via Flatpak and my Library was located on a BtrFS subvolume. Some games randomly stopped working whcih where running fine with my previous system while other kept working. At first I thought this being related to the Flatpak runtime but a natively installed Steam client also had the same issues with the same games.

After a lot of trial and error I found out this seems to be caused by the runtimes not being 100% compatible with BtrFS. Moving the affected games and the runtimes to an XFS formatted drive instead made them work out of the box.

As OP mentioned they also have a BtrFS volume I'd like to recommend trying to run TF2 from a not BtrFS volume.

Games I encountered not working from a BtrFS volume are:

  • Age of Mythology (Steam runntime Soldier, Proton 7.0-4)
  • Satisfactory (Steam runntime Soldier, Proton 7.0-4)
  • The Sinking City (Steam runntime Soldier, Proton 7.0-4)
  • Doom Eternal (Steam runntime Soldier, Proton 7.0-4)

After moving these games to a XFS drive everything was working right with the same and also on a XFS drive located runtime and Proton version.

VortexAcherontic avatar Nov 16 '22 13:11 VortexAcherontic

Hello @VortexAcherontic, can you provide logs (content_log.txt) for the failing installs? And maybe the same game against an XFS drive for comparison?

TTimo avatar Nov 16 '22 15:11 TTimo

@TTimo it turned out this is an issue related to Proton: https://github.com/ValveSoftware/Proton/issues/6335

VortexAcherontic avatar Nov 23 '22 12:11 VortexAcherontic