protonscr

Rollback from Steam Client Beta to Steam Client forces Steam Play games to full re-downloads.

steamclosed Steam clientProton
ValveSoftware/steam-for-linux#6035 · opened 2019-01-19 by ewe2 · updated 2019-02-04 · 20 comments · github
Eewe2 2019-01-19 github

OS Linux Debian Buster/Sid (testing)
CPU I5
GPU Nvidia 1050ti
RAM 16GB
Steam Play Proton version 3.16-6 Beta

  • Steam client version (build number or date): Jan 4 2019
  • Distribution (e.g. Ubuntu): Debian Buster
  • Opted into Steam client beta?: Yes, previously
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Similar problem was seen in a note in issue #6028, similar problems with 0-sized downloads for Steam Play games and inability to reach content servers. Debian enables IPv6 by default in kernel however my ISP does not support IPv6 (Carrier NAT), so that fix is impossible.

Rolling back to the stable version (as above) causes most Steam Play games to require full re-downloads, but it also forces updates for several native games.

Steps for reproducing this issue:

  1. Roll back from Jan 16/17 Steam Client Beta to current Linux Steam Client.
DDPTJKKVH 2019-01-19 github

I can confirm this. I have experienced this just yesterday while debugging another issue.

XXakepSDK 2019-01-19 github

Temp fix:

  1. Start steam
  2. Check for updates / rollback
  3. Do not click "restart steam"
  4. Press steam -> offline mode
  5. Press "restart"
  6. Go to settings and check 'use proton for all titles"
  7. Press "restart"
  8. Press "go online"
Kkisak-valve maintainer 2019-01-19 github

That makes this sound related to #5901.

Eewe2 2019-01-19 github

That makes this sound related to #5901.

Technically no, Steam Play isn't being disabled as far as I can see, but the stable client appears to assume it's applying to all games whether or not you have enabled that in the Beta client. But it's probably a side-effect of whatever is going on.

Ooblitum 2019-01-19 github

DAMMIT! Whatever it did it's now going to redownload all the games.............. Such nightmare. Thanks Valve.

Eewe2 2019-01-19 github

DAMMIT! Whatever it did it's now going to redownload all the games.............. Such nightmare. Thanks Valve.

Try that fix mentioned above and let us know if it works for you.

Ooblitum 2019-01-19 github

@ewe2 I tried, it didn't.

Ooblitum 2019-01-19 github

@ewe2 to be exact, I didn't know of that at first. The games were running fine, but then I happened to hit the steam play tab and noticed the checkbox for running all games on proton wasn't checked anymore (it was before), then I checked it and on restart it started to download all the damn games, and then it looks like there was no way back. I tried the procedure above but didn't help, I tried to uncheck the checkbox (since the games were running before), but now they don't run anymore with it unchecked, looks like I have to download terabytes of data for nothing.

DDPTJKKVH 2019-01-19 github

It didn't work for me either. I think you must pull it off the first time.

If you run into this issue unprepared (like most will) you are doomed. I already downloaded Valkyria Chronicles (18GB) at least three times since yesterday becuase I helped debugging the IPv4/6 issue with content servers.

I think Valve must inplement a whole new logic into the system so it is able to deal with two builds of the same game simultaneously.

Ooblitum 2019-01-19 github

Yeah, from disk avail size increase, all games simply ended up deleted when I first checked the "run all games in proton" checkbox and restarted.

For me it indeed relates to #5901.

UUradamus 2019-01-22 github

The mentioned fix doesn't help anything for me either. After allowing a beta client update earlier, all my Proton games got queued to redownload, which is totally unacceptable. I've got like ~60 games I installed to test Proton over the past few months, I'm leaving this trash on pause until this is sorted, otherwise I'm just uninstalling them all as I'm not going to blow through all that bandwidth in a day or two and face throttling over this nonsense.

Ooblitum 2019-01-22 github

@Uradamus if you're just waiting for confirmation it got fixed and you're safe to download it all again, then fine, but if you're expecting the client will magically not have to re-download all the games anymore where they simply got deleted already, not a chance.

UUradamus 2019-01-22 github

Blah, so it did delete them all. What the shit, Valve, get your act together. I only noticed that it was starting to redownload stuff shortly before I went to bed last night, didn't even think to check what was going on in the Steam dir. When I saw all those games queued up and a dozen or so smaller ones already pushed through I paused it and came here looking for answers before shutting things down in disgust. I guess I'll have to go through and remove the ones I don't care about and let the rest run an hour or two a day until things are mostly restored...

Eewe2 2019-01-24 github

Yeah best to stay on the stable client until all this is sorted. I am a most unwilling guinea pig for galaxy brain updates.

Ooblitum 2019-01-25 github

Yeah, seriously, I confirm, I didn't follow the advice and was re-downloading Batman 17GB that just finished (the client got updated once meanwhile). Then just after the download ends, only then, the client instead of finishing just put it as "paused canceled", I click download so it actually finishes the thing and it starts downloading it from scratch all over, WTF!!!!! Just wait for this issue to get closed/resolved.

JJohnanater 2019-01-27 github

Verifying the games will stop them from re-downloading.

Ooblitum 2019-01-27 github

Won't work when they simply get erased.

JJohnanater 2019-01-27 github

They only got erased when they started to download, which was one at a time. For me at least.

DDPTJKKVH 2019-02-04 github

@kisak-valve This is fixed in Steam-Beta.

If you tell me that the latest stable release had a patch included for this issue I can test it for you.

Kkisak-valve maintainer 2019-02-04 github

The 2019-02-01 Steam update has brought the stable client in line with the previous beta, so this issue should no longer be reproducible. Closing as resolved.

Nothing extracted yet.