Hello @Gullible2935, this reads more like a video driver issue or a distro packaging issue of that driver. In general, the NVIDIA proprietary driver requires that the driver's running kernel module, 32 bit userspace libraries, and 64 bit userspace libraries are all installed and exactly the same version to work properly.
I'd double check those packages with something like apt policy nvidia-dkms-580 nvidia-dkms-580-open libnvidia-gl-580 libnvidia-gl-580:i386.
Beyond that, general video driver install issues are something to ponder with you're distro's community. Closing as not a Steam client issue.
Hello @kisak-valve ,
Thank you for pointing me in that direction.
I checked the NVIDIA kernel module and both 64-bit and 32-bit userspace libraries as you suggested.
Everything appears to be installed and exactly matched to version 580.173.02:
libnvidia-gl-580:amd64 = 580.173.02libnvidia-gl-580:i386 = 580.173.02libnvidia-compute-580:amd64 = 580.173.02libnvidia-compute-580:i386 = 580.173.02libnvidia-decode-580:amd64/i386 = 580.173.02libnvidia-encode-580:amd64/i386 = 580.173.02nvidia-kernel-common-580 = 580.173.02nvidia-kernel-source-580 = 580.173.02The kernel module is provided by Ubuntu's precompiled module package:
linux-modules-nvidia-580-7.0.0-30-generic
and:
modinfo nvidia
filename: /lib/modules/7.0.0-30-generic/kernel/nvidia-580/nvidia.ko
version: 580.173.02
I also checked the actual GLX libraries. Both architectures point to the same driver version:
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
-> libGLX_nvidia.so.580.173.02
/usr/lib/i386-linux-gnu/libGLX_nvidia.so.0
-> libGLX_nvidia.so.580.173.02
ldconfig also shows both 32-bit and 64-bit NVIDIA libraries at 580.173.02.
So based on your suggestion, the NVIDIA kernel module, 32-bit userspace libraries and 64-bit userspace libraries all appear to be installed and version-matched.
The original Proton problem still occurs, however.
The Proton log reports:
err:winediag:nodrv_CreateWindow
Application tried to create a window, but no driver could be loaded.
err:winediag:nodrv_CreateWindow
The explorer process failed to start.
This happens after:
Loaded "C:\windows\system32\winex11.drv"
The system itself is running X11 normally (DISPLAY=:0, XDG_SESSION_TYPE=x11), Vulkan correctly detects the Quadro P600 with NVIDIA 580.173.02, and nvidia-smi also works correctly.
So the problem does not appear to be caused by a version mismatch between the NVIDIA kernel module and the 32/64-bit userspace libraries.
Could there be another NVIDIA 580 / hybrid graphics / PRIME-on-demand issue that would cause Wine/Proton to reach winex11.drv but then fail with nodrv_CreateWindow?
Thank you.
proton experimentalx1 2026-09PROTON_LOG=1x1 2026-09amdxcffx64.dllx1 2026-09
Your system information
steam-logs.tar.gz
Hello,
I am having a serious problem with Steam Play / Proton on Kubuntu 24.04. The problem affects multiple Proton games, not just one particular title.
I have already done quite a lot of troubleshooting and I would like to ask whether this could be a Steam/Proton regression, Steam Runtime problem, or an issue related to the current NVIDIA 580 driver and hybrid Intel/NVIDIA graphics setup.
System
on-demandexperimental-11.0-20260826-x86_64How the problem started
Originally, I was using an older NVIDIA driver (535.x, I believe). Steam and my Proton games worked normally.
After the NVIDIA driver was upgraded to the 580 branch, problems started.
At first I suspected an NVIDIA driver/kernel issue because switching the laptop to: sudo prime-select nvidia
and then launching Steam caused the X11 session to crash and return me to the login screen.
Switching back to: sudo prime-select on-demand
made the desktop stable again.
However, the games still do not work correctly in
on-demandmode.Important: this is not limited to one game
I have tested multiple Proton games and the problem is not specific to Simt Simulator.
One particularly useful example is Euro Truck Simulator 2, which I also run through Proton.
With ETS2, the following happens:
This behavior is reproducible enough that I am now concerned that this may be a problem in the Proton / graphics stack rather than an issue with an individual game.
Other Proton games simply fail to start without reaching the game at all.
NVIDIA / Vulkan checks
nvidia-smireports:NVIDIA-SMI 580.173.02
Driver Version: 580.173.02
CUDA Version: 13.0
GPU: Quadro P600
Memory: 4096 MiB
The GPU is detected correctly.
vulkaninfo --summaryalso detects both GPUs:GPU0:
Intel(R) UHD Graphics 630 (CFL GT2)
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.2.8-0ubuntu0.24.04.2
GPU1:
Quadro P600
driverName = NVIDIA
driverInfo = 580.173.02
GPU2:
llvmpipe
So the NVIDIA Vulkan driver is installed and the Quadro P600 is visible to Vulkan.
The current PRIME configuration is:
prime-select query
on-demand
The session is:
XDG_SESSION_TYPE=x11
DISPLAY=:0
WAYLAND_DISPLAY=
X11 access control is normal: access control enabled, only authorized clients can connect
SI:localuser:ondra
and the X11 socket exists:
/tmp/.X11-unix/X0
Steam itself works
Steam itself launches normally.
Interestingly,
nvidia-smishows that Steam and Steam WebHelper are actually using the NVIDIA GPU:/usr/lib/xorg/Xorg
steam
steamwebhelper
steamwebhelper
So NVIDIA PRIME offloading is definitely functioning at least for Steam.
Steam also correctly detects both GPUs:
Intel(R) UHD Graphics 630
driver: Mesa
Quadro P600
driver: NVIDIA proprietary
driver version: 580.173.02
llvmpipe
Therefore this does not look like a simple case where Steam cannot see the NVIDIA GPU.
Proton test
I tested Proton Experimental: experimental-11.0-20260826-x86_64
At one point Proton Experimental managed to start one of the games, but the game had a completely incorrect/unusable resolution. Subsequent attempts failed again.
I also explicitly tested NVIDIA PRIME offloading with: __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only %command%
The game still did not start.
During that test,
nvidia-smishowed Steam and Steam WebHelper using the Quadro P600, confirming that the NVIDIA GPU was actually active.Proton log
I enabled:
PROTON_LOG=1 %command%
This created:
steam-12822364823446618112.log
The Proton log reports:
Proton:
1787725910 experimental-11.0-20260826-x86_64
The most significant error is: err:winediag:nodrv_CreateWindow
Application tried to create a window, but no driver could be loaded.
err:winediag:nodrv_CreateWindow
The explorer process failed to start.
This happens after Wine has already loaded: Loaded "C:\windows\system32\winex11.drv"
There is also:
err:steamclient:steamclient_init_registry
Failed to connect to Steam
and:
Proton: Error: unable to use parent for game drive, path
There is also this message:
Proton: Error while copying to
".../compatdata/2985439455/pfx/drive_c/windows/system32/amdxcffx64.dll":
No such file or directory
The log then continues with many Wine processes being started, but the game never creates a usable window.
Things I have already tested
prime-select on-demandprime-select nvidiavulkaninfo --summarycorrectly detects the Quadro P600 using NVIDIA 580.173.02.nvidia-smi, confirming that the NVIDIA GPU is actually being used.PROTON_LOG=1My main question
Could this be a regression or compatibility problem in the current Proton / Steam Runtime / Wine stack when running:
The particularly suspicious part is:
err:winediag:nodrv_CreateWindow
Application tried to create a window, but no driver could be loaded.
err:winediag:nodrv_CreateWindow
The explorer process failed to start.
even though:
winex11.drvis loaded,nvidia-smiworks,Additionally, Euro Truck Simulator 2 can sometimes run after the first launch, but can then completely lock up the system, requiring a REISUB reboot, after which the game may no longer start.
I would therefore like to know whether this behavior matches any known issue in Proton, Steam Runtime, Wine, DXVK/VKD3D, or the NVIDIA 580 driver.
I am especially interested in determining whether this is a known regression introduced by the recent Proton / Steam / NVIDIA updates.
I can provide the complete Proton log and any additional diagnostic output you need.
Thank you very much for your help.