580.65.06 Fixed a bug that could cause Vulkan applications to hang when destroying swapchains after a lost device event. Fixed a bug that could allow atomic commit and other DRM operations to return success status despite having failed due to handling an interrupt: nv_drm_atomic_commit can silently fail due to down_interruptible in nvkms_ioctl_common being interrupted, causing the Jay wayland compositor to hang · Issue #832 · NVIDIA/open-gpu-kernel-modules · GitHub Fixed a bug that could cause GTK 4 applications to crash when using the Vulkan backend on Wayland. Fixed a bug that could intermittently cause llama.cpp to crash on exit when using the Vulkan backend: Misc. bug: Inconsistent Vulkan segfault · Issue #10528 · ggml-org/llama.cpp · GitHub Added support for the fifo-v1 Wayland protocol on Vulkan. Updated GPU clock value reporting in nvidia-settings, NVML, and nvidia-smi to show clocks before thermal and idle slowdowns for better consistency with the equivalent functionality on Windows. Fixed compatibility with Bigscreen Beyond Head Mounted Displays. Fixed a bug that could result in a black screen when setting specific modes on HDMI displays. Fixed a bug that caused blank or frozen screens under the following conditions: nvidia-drm is loaded with the modeset=1 and fbdev=1 parameters, using a Maxwell or Pascal series GPU, and more than one display device of differing resolutions are connected. Fixed a bug that caused nvidia-suspend.service to fail when available system memory is low. Enabled RMIntrLockingMode by default. This feature can help reduce stutter especially when using virtual reality. This feature was originally introduced in the r570 series. It can be disabled by loading nvidia.ko with the NVreg_RegistryDwords=RMIntrLockingMode=0 kernel module parameter. Implemented another feature that can reduce time spent in the interrupt top half for low latency display interrupts by deferring the work until later. This feature is experimental and disabled by default. This feature can be enabled by loading nvidia.ko with the NVreg_RegistryDwords=RmEnableAggressiveVblank=1 kernel module parameter. Fixed a bug that could cause blank rendering on some single-buffered GLX applications when running on Xwayland. Fixed a bug that could cause a kernel use-after-free on pre-Turing GPUs. Fixed a bug that could cause OpenGL applications and compositors to stall when using NVIDIA as a PRIME Display Offload sink (“Reverse PRIME”), potentially resulting in a black screen. Fixed a bug that led to increasing memory usage in X11 OpenGL and Vulkan applications after suspend/resume cycles. Fixed a bug that could cause 32-bit x86 applications running on recent builds of glibc to crash on dlopen().

I can reproduce this. I filed internal bug #5436037.

Most DXVK games do not run, vkd3d games do not run, mangohud overlay missing, steam overlay not working, obs-vkcapture does not work… Some games still start but I think this affects games that require specific features. See Elite Dangerous (359320) · Issue #150 · ValveSoftware/Proton · GitHub for an example.

Is NVML PowerMizer supported on Windows too? What’s the relationship between it and the nvidia control panel setting? Is it different than before?

Tried a few games: HZD Remastered, TLOU, and L4D2. The games seem to run ok without issue in Wayland and NTsync. I enabled NVreg_RegistryDwords=RmEnableAggressiveVblank=1 The games all ran fine and smooth. HZD Remaster though it looked like I got a 10-20 FPS bump. Before I was getting around 105 and now it is 120 ish. This is maxed out settings at 4K with DLAA. I will keep testing my library and will report if I come across any issues. The only GTK4 app I have on my system is Handbrake. As far as I can tell, it runs ok. The only thing borked is the window decoration for close because it will hang the program. If I quit the application through the File menu, it works fine. [Screenshot_20250804_214455] The only oddity since enabling the agressive vblank is that it looks like when opening a child window sometimes (open/save file browser), the screen will go black for a few seconds.

GTK applications freeze on close.

Fixed a bug that could cause GTK 4 applications to crash when using the Vulkan backend on Wayland. I don’ know what’s fixed, but now GTK4 application are unusable on Vulkan. Here’s quick fix if someone have that problem: echo "export GSK_RENDERER=ngl" >> ~/.profile

with the 580 beta driver, everytime I try to close gtk4 apps they hang, and I’m not using the vulkan backend, I’m using the automatic renderer in KDE Plasma 6.4 which is OpenGL. nvidia-bug-report.log.gz (888.5 KB)

[image] naeq3d: GTK4 application are unusable on Vulkan [image] agarplayerarlon: with the 580 beta driver, everytime I try to close gtk4 apps they hang Scroll up. Read thread.

Any chance we might see the vk hdr changes so that vk_hdr_layer is no longer necessary in 585? VK_EXT_swapchain_colorspace VK_EXT_hdr_metadata

580 release feedback & discussion

Graphics / Linux Linux

zebcom August 5, 2025, 5:08am 19

I think this is related to the GTK4 close bug, but when using video player mpv, no controls work, and it does not close either (without forcing)..

Topic		Replies	Views
Summary of existing issues with the nVidia proprietary driver Linux nvbugs , linux-driver	17	5134	January 21, 2026
610 release feedback & discussion Linux	301	42893	October 12, 2026
570 release feedback & discussion Linux	657	68408	March 3, 2026
590 release feedback & discussion Linux	462	47017	November 6, 2026
575 release feedback & discussion Linux	507	56228	May 28, 2026
595 release feedback & discussion Linux	513	56404	October 25, 2026
560 release feedback & discussion Linux	563	59019	November 18, 2025
550.78 release feedback & discussion thread Linux	21	5493	June 26, 2024
Hangs/Freezes when Vulkan v-sync (VK_PRESENT_MODE_FIFO_KHR) is enabled Linux	39	15589	January 11, 2021
555 release feedback & discussion Linux	275	51823	January 10, 2025

580 release feedback & discussion

Related topics