Yeap, same issue for me, starting this driver ver. Star Citizen gives me the exact same error. Didn’t have this issue previously.
The issue is back with this update I guess. Previously the game straightaway crashed.
Wuthering Waves crashes after some time of playing when launched with PROTON_VKD3D_HEAP=1 VKD3D_CONFIG=descriptor_heap. Game does load and I can play for some time before it freezes and 30s later I get a dialog box saying “application has hung and will terminate”. My entire system freezes for 10s as well. Using latest proton-cachyos build.
The exploding meshes bug (5649065) is still plaguing v595.71.05:
What is the status of this bug, please: any progress on its resolution ? It has been 9 months that I reported it, and it is a show stopper bug.
nvidia-bug-report.log.gz (360.5 KB)
are you sure that’s a bug? I’ve seen this behavior in failing hardware
Yes this time I suppose it’s a bug coming from kurogames. Instantly appeared since v3.3 was released and all linux users (whatever the distro) who used to play with ray-tracing enabled have the 80% crash, even with AMD gpu
It happens on two different computers, with two different GPU models, and it only happens with v580 and newer drivers (v575 and older drivers work just fine, and I am actually stuck with 575.64.05 to be able to use NVIDIA cards under Linux).
Also under Windows and with the latest Windows drivers (596) this bug does not happen, while in the exact same conditions (same hardware, same exact OpenGL “viewer” but compiled for Windows instead of Linux, and rendering the same scene with the same renderer settings).
@zyli3 use packages from the DC repo, just like the wiki advises, it works perfectly fine:
morgwai@morgwai-x4tuxedo:~$ sudo dkms status
nvidia/595.71.05, 6.12.85+deb13-amd64, x86_64: installed
nvidia/595.71.05, 6.18.15+deb13-amd64, x86_64: installed
nvidia/595.71.05, 6.19.13+deb13-amd64, x86_64: installed
nvidia/595.71.05, 7.0.3+tbfive1-amd64, x86_64: installed
(I’ve just rebuilt from “proprietary” to “open” flavour to make sure both compile fine).
Apologies for the post again about the sharpness, but it seems that something has happened and now both the sharpness and the nvidia image scaling(NIS) in gamescope barely have any effect - it is like it’s absent or at best when you crank it to the max you barely notice a difference. This was not the case which leads me to believe that there is some regression going on with how the driver interacts with upscaling via NIS and sharpness - could also be something from the windows driver carried over(afaik they share codepaths).
In short - both sharpness in the nvidia settings + nv variable work and to a very minimal effect NIS(Nvidia image scaling) via gamescope - this one doesn’t work the upscaling only applies slight sharpness effect, triple checked there was no change and last NIS is 1.0.3 from years ago.
EDIT: Decided to edit the post instead of double posting about this.
So after very thorough tests, it appears both the sharpness is working and NIS - it is just very selective on which surfaces it is visible:
no sharpness:
sharpness 100%:
In similar fashion same applies to the NIS - when you use it for a game it works, but outside of that it doesn’t seem to affect much:
NIS disabled just the game:
NIS enabled via gamescope default sharpness:
Thanks for the information.
Driver version 595.71.05 introduces only one change, and it concerns Wayland, which I don’t use.
I use Xfce4 and Cinnamon, so I have no qualms about using the previous version, 595.58.03.
I’ll wait until next month – maybe they’ll fix this collision with the Debian kernel.
The current setup, i.e., only the necessary Debian entries in ‘sources.list’ + the ‘*run’ NVidia driver file from nvidia.com, is, in my opinion, the ideal solution, which I’ve been using for many years.
I’m surprised that the latest Nvidia driver in the Debian repository is some oldie (550.163.01-5 from 2025-04-09, derived from 2024-01-19, https://download.nvidia.com/XFree86/Linux-x86_64/550.40.07/) that doesn’t support RTX 50xx cards.
Apparently, Debian developers are having some trouble with this, although others (OpenSuse, Arch) don’t.
You may need to use the NVidia repository in the future (https://developer.download.nvidia.com/compute/cuda/repos/debian13/x86_64/), but for now, it’s not necessary.
Thanks again for the information.
Best regards.
Postscript
I’m familiar with your website: https://wiki.debian.org/NvidiaGraphicsDrivers
It’s very good – it should be a model for others.
There’s nothing to be fixed:
-
Debian’s kernel 6.12.85 package works as intended.
-
Nvidia’s deb packages for Debian with driver v595.71 work as intended.
-
dot-run installer is not guaranteed to work on Debian or any other particular distro. There’s even a disclaimer at the top of each dot-run download page:
Note that many Linux distributions provide their own packages of the NVIDIA Linux Graphics Driver in the distribution’s native package management format. This may interact better with the rest of your distribution’s framework, and you may want to use this rather than NVIDIA’s official package.
(emphasis mine)
As you can clearly see by this very example, it’s far from ideal ;-]
Running fedora silverblue 44 with 595.71.05, and ‘EVE Online’ loads but freezes when trying to open a window such as ‘fitting’. The game ran fine with 580. This issue is not isolated to EVE, and is also reported here winevulkan:signaller_worker wait timed out spam since latest update in some games · Issue #4408 · ublue-os/bazzite · GitHub
I’m running GE-proton-10-34
The console output shows this at the time of freeze ‘err:winevulkan:signaller_worker wait timed out with non-empty poll list.’
I have some further information regarding this issue, which is present in 595.71.05, but now in 580 on fedora silverblue (and likely others). If you set the ‘shaders’ to ‘low’ you’re able to play the game without it crashing. Setting shaders to either ‘medium’ or ‘high’ your game will crash when opening for example the ‘fitting’ window. To clarify, in EVE online setting shaders to Low basically turns the shaders off and everything just becomes greyscale. Its not an option, but you can play.
It would be nice if NVIDIA addressed the reports in this thread about Ray Tracing issues in some games, which crash after it is enabled. This is a regression typical of the 590/595 driver branches, and it would be nice if it were finally fixed.
I’ve done some additional testing here. Switching to DirectX11 from 12 resolves the issue. Once set to DirectX11 I can successfully use ‘shader quality’ set to either medium or high.
This was working fine with DirectX12 on 580 driver
[FIX] Wuthering Waves – Ray Tracing crash at 75-80% loading on Linux (CachyOS / GE-Proton)
If you’re running Wuthering Waves on Linux with GE-Proton and ray tracing causes the game to crash at around 75-80% of the loading screen, here’s how to fix it.
Credit: originally reported by kchoukai on ProtonDB.
Setup
- Distro: CachyOS (Arch-based)
- GPU: NVIDIA RTX 4000 series
- Proton: GE-Proton10-34 (“Proton-GE Latest”)
- Kernel: 7.0.3-1-cachyos-bore
The problem
Enabling ray tracing causes the game to freeze and crash during the loading screen at ~75-80%. The only workaround was to disable RT via engine.ini and in-game settings.
Why GE-Proton is required
The game can technically launch on Linux without any compatibility layer using just SteamOs=1 in launch options, but the anti-cheat kicks in after a moment and kills the process. GE-Proton includes specific patches that allow the game to run without being detected and closed by the anti-cheat.
The fix: update vkd3d-proton to 3.0.1
-
Install GE-Proton if you haven’t already:
Releases · GloriousEggroll/proton-ge-custom · GitHub -
In Steam, right-click Wuthering Waves → Properties → Compatibility → select GE-Proton.
-
Download the latest vkd3d-proton release (3.0.1) from:
Releases · HansKristian-Work/vkd3d-proton · GitHub
Grab the.tar.zstfile (pre-built binaries, no compilation needed). -
Extract the archive:
tar -xf vkd3d-proton-3.0.1.tar.zst
cd vkd3d-proton-3.0.1
- Copy the new DLLs into your GE-Proton installation (adjust the path to match your actual Proton-GE folder):
cp x64/d3d12.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/vkd3d-proton/x86_64-windows/
cp x64/d3d12core.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/vkd3d-proton/x86_64-windows/
cp x86/d3d12.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/vkd3d-proton/i386-windows/
cp x86/d3d12core.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/vkd3d-proton/i386-windows/
-
Leave Steam launch options empty, or add your usual options.
-
Enable Ray Tracing in-game, no more crash!
Notes:
- This fix only works with GE-Proton, not with standard Proton versions.
- Back up the original DLLs before copying if you want to be safe (add .bak extension).
Hope this helps someone!
Someone found the NVIDIA 595.71.05 driver fails to build via DKMS on Debian https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/585855/nvidia-5957105-dkms-build-failure-on-kernel-612x-p/ And I found that this bug also occur when building NVIDIA 580.159.03 driver via DKMS on Debian. The lack on execute permission of pahole.sh causes this error.
Please fix the error.
Log
LD [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-drm.ko
LD [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-peermem.ko
BTF [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-peermem.ko
/bin/sh: 1: /var/lib/dkms/nvidia/580.159.03/build/pahole.sh: Permission denied
make[4]: *** [/usr/src/linux-headers-6.12.86+deb13-common/scripts/Makefile.modfinal:64: /var/lib/dkms/nvidia/580.159.03/build/nvidia-peermem.ko] Error 126
make[4]: *** Deleting file '/var/lib/dkms/nvidia/580.159.03/build/nvidia-peermem.ko'
make[4]: *** Waiting for unfinished jobs....
BTF [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-drm.ko
/bin/sh: 1: /var/lib/dkms/nvidia/580.159.03/build/pahole.sh: Permission denied
make[4]: *** [/usr/src/linux-headers-6.12.86+deb13-common/scripts/Makefile.modfinal:64: /var/lib/dkms/nvidia/580.159.03/build/nvidia-drm.ko] Error 126
make[4]: *** Deleting file '/var/lib/dkms/nvidia/580.159.03/build/nvidia-drm.ko'
BTF [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-modeset.ko
/bin/sh: 1: /var/lib/dkms/nvidia/580.159.03/build/pahole.sh: Permission denied
make[4]: *** [/usr/src/linux-headers-6.12.86+deb13-common/scripts/Makefile.modfinal:64: /var/lib/dkms/nvidia/580.159.03/build/nvidia-modeset.ko] Error 126
make[4]: *** Deleting file '/var/lib/dkms/nvidia/580.159.03/build/nvidia-modeset.ko'
BTF [M] /var/lib/dkms/nvidia/580.159.03/build/nvidia-uvm.ko
/bin/sh: 1: /var/lib/dkms/nvidia/580.159.03/build/pahole.sh: Permission denied
make[4]: *** [/usr/src/linux-headers-6.12.86+deb13-common/scripts/Makefile.modfinal:64: /var/lib/dkms/nvidia/580.159.03/build/nvidia-uvm.ko] Error 126
make[4]: *** Deleting file '/var/lib/dkms/nvidia/580.159.03/build/nvidia-uvm.ko'
make[3]: *** [/usr/src/linux-headers-6.12.86+deb13-common/Makefile:1914: modules] Error 2
make[2]: *** [/usr/src/linux-headers-6.12.86+deb13-common/Makefile:236: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.12.86+deb13-amd64'
make[1]: *** [Makefile:236: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.12.86+deb13-common'
make: *** [Makefile:115: modules] Error 2