Hello @lsr1006, it might be useful for a Steam dev if you noted what filesystem is being used with ~/Games/SteamLibraryHDD (The Steam library folder mentioned in content_log.txt with 455130).
Skimming over that log, I didn't see any strong hints to help a Steam dev ponder this riddle.
Good point, I should have mentioned that.
~/Games/SteamLibraryHDD is a symlink which points to a SteamLibrary on a EXT4 partition. This is the library location where I have installed both the base game and the mod tools.
In case it may be of any importance, my OS is installed on a BTRFS partition, which is where my other SteamLibrary is.
Also having the same issue. In fact, the download stalls in the same exact place as OP's download did.
Distro: Arch Linux (x86_64)
Steam Build: 1731433018
I am not
using the Steam beta and I have already verified that all my packages are up to date. My games drive is formatted in EXT4, as well as my root partition.
Log files: logs.tar.gz
is there any fix to this yet?
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Unable to download 'Call of Duty: Black Ops III - Mod Tools' through Steam on Linux.
Though I am aware that the Black Ops III - Mod tools may not be intended to run on Linux, I wanted to attempt to download them and try to run them using Proton. The tools do download but the process fails around 50% during the "Installing" step. The disk and network usage drop to 0 and the time remaining estimate keeps increasing into the months. I have let it sit for some time with no progress.
Canceling the download while in this stuck state is also a pain. I was unable to cancel the install process from the downloads screen so I had to restart Steam several times and clear the download cache before I was finally able to remove it from the download queue and then "uninstall" it.
Troubleshooting: I have tried clearing the download cache, verifying the game files for Black Ops 3, and retying the whole process several times. Might there be any way to work around this issue so I can complete the download and try running the mod tools with Proton?
Steps for reproducing this issue: