You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much of this information comes from 32- and 64-bit copies of the wflinfo utility. If you get a shell inside the Snap environment, you can run them like this:
Running with LD_DEBUG=files in the environment reveals why: /var/lib/snapd/lib/gl32/libGLX_nvidia.so.0 requires libnvidia-glsi.so.535.154.05 which is not found anywhere in the search path.
When running Steam Linux Runtime or Proton games, this manifests as a warning like this one, as also seen on #347:
i386-linux-gnu-capsule-capture-libs: warning: Dependencies of libGLX_nvidia.so.0 not found, ignoring: Missing dependencies: Could not find "libnvidia-glsi.so.535.154.05" in LD_LIBRARY_PATH "/snap/steam/171/graphics/lib/i386-linux-gnu:/snap/steam/171/graphics/usr/lib:/snap/steam/171/usr/lib/i386-linux-gnu:/snap/steam/171/lib/i386-linux-gnu:/snap/steam/171/usr/lib/i386-linux-gnu/pulseaudio:/snap/steam/171/usr/lib/x86_64-linux-gnu/alsa-lib:/snap/steam/171/usr/lib/x86_64-linux-gnu/pulseaudio:/snap/steam/171/graphics/usr/lib/i386-linux-gnu:/snap/steam/171/graphics/usr/lib/x86_64-linux-gnu:/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl/vdpau", ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib
Similarly, running the i386-linux-gnu-check-vulkan diagnostic helper (in the same directory) with no arguments reveals that 32-bit Vulkan is broken, and running it under LD_DEBUG=files shows us why:
29797: file=libnvidia-glsi.so.535.154.05 [0]; needed by /var/lib/snapd/lib/gl32/libGLX_nvidia.so.0 [0]
but that library cannot be found.
Expected Behavior
Accelerated 32-bit graphics drivers should be provided. These are required by 32-bit games, either native Linux games or Windows games via Proton.
I would have expected that the maintainers of this app would have noticed these warnings during testing and rectified the situation, before recommending this app to the public. This is a regression when compared with installing Steam as a .deb package.
Steps To Reproduce
Open Steam's Help -> Steam Runtime Diagnostics and look for indications of potential brokenness.
Or, try to launch a 32-bit game and observe it running slowly.
Environment
"Unable to collect hardware information due to missing plugs"(This is an Ubuntu 22.04 system with an Nvidia GTX 1080, which works correctly in a non-Snap environment.)
gaming-graphics-core22 version
kisak-fresh (default)
Anything else?
No response
The text was updated successfully, but these errors were encountered:
I can confirm this is still a problem today. All of Valve's older titles that are still 32-bit (such as Half-Life (1, 2 and the Episodes), Portal, Portal 2, Counter-Strike: Source...) are unable to use the NVIDIA card. On laptops, this will cause the game to fall back to the Mesa implementation running on the integrated Intel chipset silently.
EDIT: My comment seems to be ill-timed; this issue is apparently tied to the way snapd provides the host libs to the container and 2.63.1 should be released very soon to fix this: canonical/snapd#14308
Ensure there isn't an existing issue for this and check the wiki
Current Behavior
To reproduce, open Steam's Help -> Steam Runtime Diagnostics.
On a working system, you should have both i386 and x86_64 accelerated GLX, EGL and Vulkan drivers, and ideally also VDPAU.
Steam has a diagnostic tool for this, which means it should be very easy to verify whether the Snap app and Valve's official .deb work equally well.
In this Snap app, 64-bit drivers seem to be OK (VA-API is missing, but that's normal for Nvidia):
but 32-bit Vulkan doesn't work:
32-bit VDPAU is just entirely missing:
32-bit GLX loads a software renderer:
and 32-bit EGL doesn't work:
Much of this information comes from 32- and 64-bit copies of the wflinfo utility. If you get a shell inside the Snap environment, you can run them like this:
Running with
LD_DEBUG=files
in the environment reveals why:/var/lib/snapd/lib/gl32/libGLX_nvidia.so.0
requireslibnvidia-glsi.so.535.154.05
which is not found anywhere in the search path.When running Steam Linux Runtime or Proton games, this manifests as a warning like this one, as also seen on #347:
i386-linux-gnu-capsule-capture-libs: warning: Dependencies of libGLX_nvidia.so.0 not found, ignoring: Missing dependencies: Could not find "libnvidia-glsi.so.535.154.05" in LD_LIBRARY_PATH "/snap/steam/171/graphics/lib/i386-linux-gnu:/snap/steam/171/graphics/usr/lib:/snap/steam/171/usr/lib/i386-linux-gnu:/snap/steam/171/lib/i386-linux-gnu:/snap/steam/171/usr/lib/i386-linux-gnu/pulseaudio:/snap/steam/171/usr/lib/x86_64-linux-gnu/alsa-lib:/snap/steam/171/usr/lib/x86_64-linux-gnu/pulseaudio:/snap/steam/171/graphics/usr/lib/i386-linux-gnu:/snap/steam/171/graphics/usr/lib/x86_64-linux-gnu:/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl/vdpau", ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib
Similarly, running the
i386-linux-gnu-check-vulkan
diagnostic helper (in the same directory) with no arguments reveals that 32-bit Vulkan is broken, and running it underLD_DEBUG=files
shows us why:but that library cannot be found.
Expected Behavior
Accelerated 32-bit graphics drivers should be provided. These are required by 32-bit games, either native Linux games or Windows games via Proton.
I would have expected that the maintainers of this app would have noticed these warnings during testing and rectified the situation, before recommending this app to the public. This is a regression when compared with installing Steam as a .deb package.
Steps To Reproduce
Open Steam's Help -> Steam Runtime Diagnostics and look for indications of potential brokenness.
Or, try to launch a 32-bit game and observe it running slowly.
Environment
gaming-graphics-core22 version
kisak-fresh (default)
Anything else?
No response
The text was updated successfully, but these errors were encountered: