protonscr

All Proton games become unusable or fail to launch on Kubuntu 24.04 with NVIDIA 580 + Quadro P600 + Intel hybrid graphics

steamclosed
ValveSoftware/steam-for-linux#13569 · opened 2026-09-02 by Gullible2935 · updated 2026-09-03 · 2 comments · github
GGullible2935 2026-09-02 github

Your system information

  • Steam client version (build number or date): 1785799196
  • Distribution (e.g. Ubuntu): Kubuntu (Ubuntu + KDE) 24.04 LTS
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs:

steam-logs.tar.gz

  • GPU: Nvidia + Intel

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

  • OS: Kubuntu 24.04
  • Desktop: KDE Plasma 5.27.12
  • Session: X11
  • X.Org: 21.1.11
  • Kernel: 7.0.0-30-generic
  • CPU: Intel Core i7-8850H
  • RAM: 32 GB
  • iGPU: Intel UHD Graphics 630 (CoffeeLake-H GT2)
  • dGPU: NVIDIA Quadro P600 Mobile (Pascal / GP107GLM)
  • NVIDIA driver: 580.173.02
  • Mesa: 25.2.8-0ubuntu0.24.04.2
  • PRIME mode: on-demand
  • Proton tested: Proton Experimental, build experimental-11.0-20260826-x86_64

How 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-demand mode.

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:

  • The first time I launch the game after boot, it can sometimes start and work normally.
  • After some time, however, the game can freeze the system so badly that the graphical session becomes completely unresponsive.
  • The machine then has to be restarted using REISUB.
  • After rebooting, trying to launch ETS2 again fails — the game no longer starts.

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-smi reports:
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 --summary also 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-smi shows 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-smi showed 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

  1. prime-select on-demand
  • Desktop remains stable.
  • Proton games still fail.
  1. prime-select nvidia
  • Launching Steam can crash the X11 session and return me to the login screen.
  1. NVIDIA 580.173.02
  • Currently installed.
  1. Vulkan
  • vulkaninfo --summary correctly detects the Quadro P600 using NVIDIA 580.173.02.
  1. Steam itself
  • Launches normally.
  1. NVIDIA PRIME offloading
  • Steam and Steam WebHelper appear in nvidia-smi, confirming that the NVIDIA GPU is actually being used.
  1. Proton Experimental
  • Does not reliably launch the games.
  1. PROTON_LOG=1
  • Reproduces the problem and produces a Proton log.
  1. Multiple Proton games
  • The problem is not specific to one game.
  • Euro Truck Simulator 2 is also affected.

My main question

Could this be a regression or compatibility problem in the current Proton / Steam Runtime / Wine stack when running:

  • Kubuntu 24.04
  • KDE Plasma 5.27
  • X11
  • Intel + NVIDIA hybrid graphics
  • PRIME on-demand
  • NVIDIA 580.173.02
  • Quadro P600 / Pascal
  • Proton Experimental 11

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:

  • X11 itself is running normally,
  • winex11.drv is loaded,
  • Steam itself works,
  • Vulkan sees the NVIDIA GPU,
  • nvidia-smi works,
  • PRIME offloading works.

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.

Kkisak-valve maintainer 2026-09-02 github

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.

GGullible2935 2026-09-03 github

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.02
  • libnvidia-gl-580:i386 = 580.173.02
  • libnvidia-compute-580:amd64 = 580.173.02
  • libnvidia-compute-580:i386 = 580.173.02
  • libnvidia-decode-580:amd64/i386 = 580.173.02
  • libnvidia-encode-580:amd64/i386 = 580.173.02
  • nvidia-kernel-common-580 = 580.173.02
  • nvidia-kernel-source-580 = 580.173.02

The 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 versions

Launch options

Launch lines

DLLs