Clearing the download cache fixes it temporarily. After a few hours (without having plugged in a controller) it seems to start happening again.
I just figured this out, and it is mostly my fault.
Attaching strace revealed
openat(AT_FDCWD, "~/.steam/debian-installation/userdata/NNNNNNNNN/ugc/download/NNNNNNNNNNNNNNNNNN/1865216935_controller_config.vdf", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0777) = -1 ENOENT
Following that path, ~/.steam/debian-installation/userdata/NNNNNNNNN/ugc/download ended up being a symlink I made a long time ago (when running out of disk space) that was now broken. Deleting the symlink and manually recreating the directory fixed this.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Steam is constantly making network requests, resulting in ~30KiB/s constant download. I am not sure when this started, but I just noticed it looking at the network graph in gnome-system-monitor.
It is constantly requesting the same two files from
steamusercontent-a.akamaihd.netevery second.These files are:
This also results in DNS queries for the domain every 5 seconds.
Both games are installed, having played Crash N Sanity Trilogy very recently. These look like default controller configs.
The URLs requested are in the form
/ugc/NNNNNNNNNNNNNNNNNN/NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN. Unsure if they contain any personally identifying IDs, and as such I am not sharing them at this time.The issue persists whether I have any controllers plugged in or not. I recently plugged in a second Steam Controller, which might have triggered this. I do not have any xbox or playstation controllers. Steam input is working fine.
I can't find any way to stop this constant request loop, or to change the behaviour in any way. I tried changing tabs (store, library), starting Big Picture, plugging and unplugging controllers, closing all steam windows, going offline in "Steam Friends".
The moment the Steam client was closed ("Exit Steam" from tray icon) is clearly identifiable due to the lack of network activity.

Steps for reproducing this issue: