Change:
/lib32 /usr/lib/i386-linux-gnu /usr/lib32 <ins> /run/opengl-driver/lib /run/opengl-driver-32/lib </ins> EOF ldconfig &> /dev/null '';

Discussion:
CloudBuilt (AppID ) fails to launch. It uses OpenGL but does not have a native Linux build so it runs via Proton. I can't remember any other game off the top of my head that I know to use OpenGL 3.2 and not have a Linux build but I imagine they would also be affected. Some suspicious lines from the journal right before Proton throws an "abort/retry/ignore" dialog and the game dies: This used to be working just fine, some change in the last 6 months broke it. Also it works with Proton 5.0 so it seems to be specifically changes related to running Proton with the newer Soldier runtime. Maintainer information:
Also having this same issue specifically with the game freeways.
i also get a similar error message where i think it's the same problem with the "unmetal" demo via steam. It says "ChoosePixelFormat failed" and googling that error message hints towards a lack of opengl contexts.
I'm having the same problem with the game Move or Die. I started using the flatpak version and it worked fine.
Is this still relevant? I have made many fixes since this was opened.
Oh nice, I will test it out.
This particular problem persists on nixos-unstable as of
which video card manufacturer do you have? for nvidia, can you try enabling modeset?
The card is an AMD Radeon RX 6600XT, using the mesa driver.
Still broken, also affects the Cyberpunk 2077 launcher
Other than confirming the problem, there is another issue with both Proton ~and regular Wine~: they are unable to use WineD3D (translation layer from Direct3D to OpenGL). EDIT: Only Proton, not Wine. You can test on Proton with by adding the launch options: . ~You can test on Wine by... not installing DXVK (which is necessary because of this issue).~ Using an AMG iGPU with Mesa.
not sure if its related, but got this error on trying to start Cyberpunk 2077 !
The CDPR launcher requires OpenGL, even though the game itself doesn't. You can work around the launcher crashing by adding to the Steam command line options, and that should start the game directly.

That does indeed work around the problem for that game, but the launcher is an easy way to reproduce the issue with a decently popular title so it is good to have listed here.
I think I know why it can't reach these libs... must be patched.
I suspect this is about the ldconfig database again. There was a lot of fiddling with that in the past too.
so, i messed around a bit with this issue today. it turns out, adding to seems to work. for 64-bit games (i tested with cs:go) running from spews out a bunch of stuff about libraries being truncated: <details<pre$ ldconfig /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: Can't link /lib/p11-kit- to /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /lib32/libSDL2- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /lib32/libSDL2- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.

34-210-bin/bin/ldconfig: Can't link /lib32/p11-kit- to /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.

34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated /nix/store/rb2yfmzdciahc6czkh7s4gaj8m56zkbr-glibc-2.34-210-bin/bin/ldconfig: file /run/opengl-driver- is truncated </pre</detailsi'm not sure why it's saying this; it seems similar to , but that issue was resolved in glibc 2.31 (we're on 2.34), and this also only seems to affect 32-bit libraries. i tried to run under a debugger, but due to optimization i wasn't able to figure out anything useful even with symbols from .
should fix this issue. please test!