protonscr

Loading chunk X failed: gamerecording.js

steamopen Steam clientWeb Component
ValveSoftware/steam-for-linux#12419 · opened 2025-11-01 by cprn · updated 2025-11-22 · 2 comments · github
Ccprn 2025-11-01 github

Your system information

  • Steam client version (build number or date): 1761786974
  • Distribution (e.g. Ubuntu): Manjaro (i3wm)
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes
  • Steam Logs: N/A
  • GPU: AMD

Please describe your issue in as much detail as possible:

I can consistently trigger this if starting Steam client on an inactive workspace:
Image

Happens about half the time (you need to hit the toc/tou race). JS components issue exists since forever, but gamerecording.js is 1st component that allows triggering it consistently.

Steps for reproducing this issue:

  1. set your DE to run Steam window on workspace A
  2. go to workspace B
  3. start Steam
  4. wait (occasionally have to switch back and forth, otherwise Steam doesn't start at all)

Example of workspace placement rule for testing in i3wm:

# $ws2: var holding your workspace 2 name
assign [title="Steam"] $ws2
Ttruefakts 2025-11-08 · hidden on GitHub github

Officially, Valve states that the .deb from steampowered.com or the Flatpak are the only supported versions of Steam. The packaged version on rpm-fusion is made by a 3rd party and valve has no control over what dependencies are bundled.

Please retest with the flatpak version of steam and attempt to reproduce. Or install Ubuntu LTS as the Readme on this repo suggests.

There is an open pull request to update the readme to better outline Steam's requirements. Please read, and cross reference the requirements against what operating system you're using on your workstation: https://github.com/ValveSoftware/steam-for-linux/pull/10424/commits/72b3eae88920635f16b30e385da0998c29f53411

Ccprn 2025-11-10 github

I'm sure someone will confirm it on different install. I know from my friends it happens to everyone, and some of them use Debian-like, some use Flathub, some even use Windows (with Nvidia's virtual workspaces), so yes, I dare say it's not something caused by system or packaging. The root cause is rendering to an inactive / unrendered surface (on an invisible workspace), which isn't something Windows people think about during QA pass, but it's something default on any Linux desktop environment.

Upstream links