Hi there! I'm the developer of Games on Whales we basically bundle Steam as a docker image so that we can then stream a virtual desktop via Moonlight.
A few users have reported this issue since yesterday, including @Diudid which was kind enough to open up this issue.

I can replicate the same problem when running the stack on my Intel ARC
logs.tar.gz

The very same machine and the same stack can run the UI perfectly when using Nvidia with the proprietary drivers instead.

I'm also experiencing the same issue on my Intel NUC. Here are my logs - wolf.log

I have very similar error running Windows version under wine.
[1107/103635.301:ERROR:viz_main_impl.cc(166)] Exiting GPU process due to errors during initialization

Native version runs fine.

Same, but i'm on amd radeon with mesa:

$ glxinfo | grep -i opengl
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 480 Graphics (radeonsi, polaris10, LLVM 19.1.3, DRM 3.57, 6.10.9-slack)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.6
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.6
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

I did several updates, mesa included, from mesa-24.2.4 to mesa-24.2.6... but i think steam also did some update, but not totally sure. opengl and vulkan are working correctly in games, so firefox and chrome, so if it is a mesa problem, it is just in some less used call

slackware-current, updated 2024/11/08 00h

Running into the same issue as OP using wolf with amdgpu (6900xt):

cat /etc/wolf/11711553324472631402/Steam/.steam/debian-installation/logs/cef_log.txt
[1108/111117.620641:WARNING:alloy_main_delegate.cc(578)] Alloy bootstrap is deprecated and will be removed in ~M127. See https://github.com/chromiumembedded/cef/issues/3685
[1108/111117.635712:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: browser
[1108/111117.636467:WARNING:task_impl.cc(31)] No task runner for threadId 0
[1108/111117.637069:WARNING:task_impl.cc(31)] No task runner for threadId 0
[1108/111117.682303:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111118.498028:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111118.498045:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 1 time(s)
[1108/111118.499514:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111118.880500:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: utility
[1108/111118.896832:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: utility
[1108/111118.932294:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: renderer
[1108/111119.188331:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111119.188350:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 2 time(s)
[1108/111119.189665:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111119.881667:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111119.881685:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 3 time(s)
[1108/111119.882974:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111120.261946:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111120.261972:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 4 time(s)
[1108/111120.263182:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111120.659143:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111120.659160:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 5 time(s)
[1108/111120.660421:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111121.055653:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111121.055673:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 6 time(s)
[1108/111121.057064:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111121.231839:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111121.231858:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 7 time(s)
[1108/111121.233182:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111121.401456:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111121.401473:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 8 time(s)
[1108/111121.402701:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1108/111121.569469:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1108/111121.569488:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 9 time(s)
[1108/111121.569499:FATAL:gpu_data_manager_impl_private.cc(449)] GPU process isn't usable. Goodbye.

Same issue on Ubuntu 24.04.1, up-to-date, AMD Ryzen 7 5800X CPU, AMD Radeon RX 6600 XT GPU

$ glxinfo | grep -i opengl
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6600 XT (radeonsi, navi23, LLVM 17.0.6, DRM 3.58, 6.8.0-48-generic)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.0.9-0ubuntu0.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.9-0ubuntu0.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.9-0ubuntu0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

$ tail .steam/logs/cef_log.txt
[1110/150429.063765:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1110/150429.214261:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1110/150429.214280:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 4 time(s)
[1110/150429.216071:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1110/150429.367407:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1110/150429.367435:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 5 time(s)
[1110/150429.369326:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1110/150429.524783:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1110/150429.524808:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 6 time(s)
[1110/150429.524820:FATAL:gpu_data_manager_impl_private.cc(449)] GPU process isn't usable. Goodbye.

I'm also affected by this and get the same logs as the rest of you. Is there any way to downgrade and lock the Steam version until this is resolved?

There's an easier way to reproduce the issue without using Wolf+Moonlight, on a Wayland host you can directly run the Steam image with:

docker run --rm -it --device=/dev/dri/renderD128 --device=/dev/dri/card0 --ipc=host --cap-add=ALL --security-opt seccomp=unconfined -e XDG_RUNTIME_DIR=/tmp -v ${XDG_RUNTIME_DIR}/${WAYLAND_DISPLAY}:/tmp/${WAYLAND_DISPLAY}:rw -e XDG_SESSION_TYPE=wayland -e WAYLAND_DISPLAY=${WAYLAND_DISPLAY} -e RUN_SWAY=true -v /tmp/SteamGOWData:/home/retro/ ghcr.io/games-on-whales/steam:edge

(On X11 should work as well by just changing the WAYLAND_ variables)

Resulting in:

You can access the exported home folder under /tmp/SteamGOWData/, which will contain the incriminating:

cat /tmp/SteamGOWData/.steam/debian-installation/logs/cef_log.txt
[1112/114848.161731:WARNING:alloy_main_delegate.cc(578)] Alloy bootstrap is deprecated and will be removed in ~M127. See https://github.com/chromiumembedded/cef/issues/3685
[1112/114848.178415:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: browser
[1112/114848.180572:WARNING:task_impl.cc(31)] No task runner for threadId 0
[1112/114848.181150:WARNING:task_impl.cc(31)] No task runner for threadId 0
[1112/114848.202414:WARNING:discardable_shared_memory_manager.cc(197)] Less than 64MB of free space in temporary directory for shared memory files: 60
[1112/114848.226382:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[1112/114848.864053:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[1112/114848.864066:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 1 time(s)
[1112/114848.865586:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process

This has been tested on latest Arch (6.11.6-arch1-1, Plasma 6.2.3) with an Intel Arc A380; if instead I use a Nvidia 3070 (with the Nvidia container toolkit) on the same system everything works correctly.

Hope this helps!

Notice that i'm not using wolf or any docker solution, my setup is a plain desktop starting steam
right now i'm unable to start steam and can only use games that do not require steam running

I'm also using Steam directly on my machine (without docker) and get the same issue (using Radeon RX 6750xt).
I also tried to start the game directly with proton, but to no avail.
Anyone got any progress on this? a workaround to still run games with proton?

For me it does not work with the wolf docker image (as mentioned above) but steam works fine starting from my desktop (sway) directly using a 6900xt.
This is with the beta client and mesa-git driver.

found a work around thanks to Abeltramo
https://github.com/ValveSoftware/steam-for-linux/issues/11406#issuecomment-2445993856
It doesn't survive a restart though,
You downgrade, then the next boot steam work.
You restart, steam autoupdate and doesn't start again.
You have to downgrade each time you want to play.

I confirm downgrading works as a workaround (which confirms it's the client that is buggy). I followed this guide : https://blog.lightwo.net/steam-client-downgrades-survival-kit.html , which explains how to prevent updates after downgrading.

Can anyone explain how to perform this workaround in Wolf? Steam is not in /usr/bin of the container so I don't know how to run it with the suggested arguments.

@SebbeM: it's /usr/games/steam

@ABeltramo et al.: this workaround snippet somewhere (ie right before actually launching steam) in the launch script (which would be here for gow/steam - I'm using my own custom image based on it) seems to do the job (putting together the previous comments):

if [ ! -f "$HOME/.steamclient-downgrade-forced" ]; then
  touch $HOME/.steamclient-downgrade-forced
  SCDG_SNAP=20241005180130
  /usr/games/steam -forcesteamupdate -forcepackagedownload -overridepackageurl https://web.archive.org/web/${SCDG_SNAP}if_/http://media.steampowered.com/client -exitsteam 
fi

STEAM_STARTUP_FLAGS="-noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles ${STEAM_STARTUP_FLAGS}"

The download should only run once (per user/session), but it's still extremely slow, and I can't blame the poor people at archive.org (which we are effectively abusing).

Sure it'd be nice if Valve themselves hosted previous Steam client builds, just in case stuff gets broken... 👀

I'm having the same problem. After some research, as other CEF apps were crashing the same way I've got the tip from the same problem in VSCode that passing --disable-accelerated-video-decode works.

However I don't know how to pass it to CEF, as steam doesn't accept it.

For people who use Wolf this will work:

Got it working, launched everytime testing five times.

It's a very very hacky method and kinda painful.

Run the container, let it download the update until you're on the main screen that just has the desktop background.

Press the > to launch a shell window.
First type in this:
rm -rf .steam
Then this command:
/usr/games/steam -forcesteamupdate -forcepackagedownload -overridepackageurl https://web.archive.org/web/20241005180130if/http://media.steampowered.com/client -exitsteam

It will take about 11 minutes to download, follow the progress and when it shuts down and says existing steam shut down the container and stop it, make sure the steam container is no longer running.

Using the steam.sh script in this pastebin (https://pastebin.com/WFqHih8k), place it wherever you want on the wolf host machine.

Then go to your HOSTS_APP_DATA folder and edit the config.toml

Update the steam app block with this:

type = "docker"
name = "WolfSteam"
image = "ghcr.io/games-on-whales/steam:edge"
mounts = ["/path/to/your/startup.sh:/opt/gow/startup-app.sh:ro"]
# keep the rest unchanged .... ```


Make sure the file is executable by anons (easier to just set it to 755)

Then run the container, everything will begin working.

If you don't want to replace steam.sh, you can add -noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles to STEAM_STARTUP_FLAGS in config.toml.

For all the guys using GOW and running Steam under Docker I'm working on a potential fix that seems to work on my Intel ARC

You'll have to manually

docker pull ghcr.io/games-on-whales/steam:fix-steam-mesa

And edit the config.toml image to point to the same tag. Please let me know how it goes here or on the dedicated PR

I can verify that the fix-steam-mesa tag works on my system with a Radeon 6600XT.

Thank you everyone for all your help in testing this, seems that the fix is working, so I've merged the PR. :edge will be pointing to the latest as before.

also found the solution for my problem (slackware64-current, no container/docker setup)

unset LIBVA_DRIVER_NAME

i had that set to LIBVA_DRIVER_NAME=vdpau long ago to test the video hardware acceleration, looks like it is now not even a valid option... and it was causing steam to crash on the GPU