After restarting Steam the same file fails due to a mismatched checksum, however Steam will eventually start (doesn't go into the update loop):
[2025-07-02 23:45:20] BVerifyInstalledFiles: bad CRC on steamrt64/steam-runtime-steamrt/steamrt3c_platform_3c.0.20250519.130919/files/share/doc/libva-x11-2/copyright (b63a8dca expected, 9ef174 actual)
I suspect this file is part of the steamrt64 manifest but not included in the package.
Unlikely, I (and presumably everyone else) have this file; the runtime wouldn't be modified after it was built on the date indicated (2025-05-19).
If I remove the file, Steam will report the same error ("-1 bytes") and download the file, without getting stuck.
To get around the checksum error temporarily, you can copy the file from ../libva2/copyright (they are identical, built from the same libva Debian source package).
To get around the checksum error temporarily, you can copy the file from
../libva2/copyright(they are identical, built from the samelibvaDebian source package).
Confirming copying ../libva2/copyright to this directory does correct the verification failure.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
I last used Steam June 30. I started Steam today, July 2, and the client began to download an update. After installing the update, it reported a verification failure and restarted the download/install procedure. It continued doing this until I terminated the process. I expected the update to install then launch the client.
I removed
~/.local/share/Steamand~/.steam. I started Steam again which downloaded the current version. This failed verification and repeated the same loop.Starting Steam from the terminal I noticed the verification failure message:
The referenced file did not exist:
I created a 5571 byte file with that name and the Steam client then correctly launched. I was able to login, download games.
I suspect this file is part of the steamrt64 manifest but not included in the package.
Steps for reproducing this issue: