protonscr

Client not respecting cloudsync setting

steamopen Steam client
ValveSoftware/steam-for-linux#7518 · opened 2020-12-09 by h1z1 · updated 2020-12-09 · 2 comments · github
Hh1z1 2020-12-09 github

Your system information

  • Steam Runtime Version: Dec 7 2020,
  • Distribution: CentOS 7
  • Have you checked for system updates?: Yes
  • Are you using the Steam Linux Runtime compatibility tool?: Yes

Please describe your issue in as much detail as possible:

Cloud sync is disabled in the steam client yet the client itself appears to completely ignore this.

Following for example is logged:

[2020-12-08 06:38:58] [AppID 7] AutoCloud checking local state for user 1111111
[2020-12-08 06:38:58] [U:1:16407428] [AppID 7] Init cache request complete
[2020-12-08 06:38:58] Starting sync job
[2020-12-08 06:38:58] [AppID 7] Starting sync (init,)
[2020-12-08 06:39:00] [AppID 7] AutoCloud checking local state for user 1111111
[2020-12-08 06:39:00] Starting sync job
[2020-12-08 06:39:00] [AppID 7] Starting sync (eval,)
[2020-12-08 06:39:00] [AppID 7] File is in sync serverbrowser_hist.vdf
[2020-12-08 06:39:00] [AppID 7] File is in sync sharedconfig.vdf
[2020-12-08 06:39:00] [AppID 7] Eval complete
[2020-12-08 06:39:00] Starting sync job
[2020-12-08 06:39:00] [AppID 7] Starting sync (down,)
[2020-12-08 06:39:00] [AppID 7] File is in sync serverbrowser_hist.vdf
[2020-12-08 06:39:00] [AppID 7] File is in sync sharedconfig.vdf
[2020-12-08 06:39:00] [AppID 7] Download complete in build list
[2020-12-08 06:39:30] Starting sync job
[2020-12-08 06:39:30] [AppID 7] Starting sync (up,)
[2020-12-08 06:39:30] [AppID 7] Need to upload file serverbrowser_hist.vdf
[2020-12-08 06:39:30] [AppID 7] File is in sync sharedconfig.vdf
[2020-12-08 06:39:31] [AppID 7] HTTP upload for file 'serverbrowser_hist.vdf' be
ginning . . .
[2020-12-08 06:39:31] [AppID 7] HTTP upload for file 'serverbrowser_hist.vdf' (o
ffset=0, length=2203) to (6.6.6.6 / 6.6.6.6., host: steamcloud-us
-west1.storage.googleapis.com), path /redactedpath?GoogleAccessId=redacted-redacted@developer.gserviceaccount.com&Expires=1607430892&Signature=redacted
success.
[2020-12-08 06:39:31] [AppID 7] Upload OK for file serverbrowser_hist.vdf
[2020-12-08 06:39:31] [AppID 7] Upload complete, result OK
[2020-12-08 06:43:54] [AppID 760] AutoCloud checking local state for user 11111
[2020-12-08 06:43:55] [AppID 438100] AutoCloud checking local state for user 11111
[2020-12-08 06:43:55] [U:1:16407428] [AppID 760] Init cache request complete
[2020-12-08 06:43:55] [U:1:16407428] [AppID 438100] Init cache request complete
[2020-12-08 06:43:55] Starting sync job
[2020-12-08 06:43:55] [AppID 760] Starting sync (init,eval,)
[2020-12-08 06:43:55] [AppID 438100] Starting sync (init,)
[2020-12-08 06:43:56] [AppID 760] Eval complete

Google Cloud is intentionally intercepted for exactly this reason. It's Evil.

Expected result is steam not sync or warn when for whatever reason it needs to.

Steps for reproducing this issue:

  1. Disable cloud sync (settings->Cloud-> uncheck both
  2. Restart steam or wait for some other process to trigger it
Ssmcv 2020-12-09 · hidden on GitHub github

I think this is probably more appropriate for https://github.com/ValveSoftware/steam-for-linux/ than this particular issue tracker.

The Steam Runtime is the library stack used by Steam and Steam games. Cloud sync might be using the Steam Runtime versions of libraries like libcurl or libssl (or it might not - I don't know exactly how it works), but the Steam Runtime is not involved in "policy" decisions like whether the Steam client wants to do cloud sync or not.

Hh1z1 2020-12-09 github

Fair enough. Just to be clear, you're saying this does not happen in Windows?

It screwed over the host when it pulled down / recreated the shaders which is why I had the damn things turned off to begin with (spawned almost 100 fossilize threads, killing steam did not stop them either).. I have no idea when it started ignoring those settings though.

Nothing extracted yet.