Summary of existing issues with the nVidia proprietary driver

[Tekstryder]

Updating this tracking thread for the nVidia 575.64.03 New Feature Branch driver release.

Currently affected by 4 issues with the proprietary nVidia Linux driver.

ALL 4 of these issues have been acked by nVidia and assigned internal tracking bug numbers.

New bug reports attached, and further details have been submitted, for each individual issue.

1. Chrome/Electron VK_ERROR_INCOMPATIBLE_DRIVER errors at launch.
   • nVidia internal tracking Bug #4882287

550.40.07 - The NVIDIA driver was unable to open 'libnvidia-glvkspirv

Greetings. Using 550-beta driver. Arch Linux. Using aur package for 550-beta-dkms. Running electron app with --ozone-platform-hint=auto flag ( vesktop for example ), I got this error in my terminal: ▶ Summary find / -type f -name “libnvidia-glvkspirv*” shows that libnvidia-glvkspirv exist in /usr/lib/libnvidia-glvkspirv.so.550.40.07

2. GTK4 application tooltips and popover dialogs are stretched/distorted/frozen. This affects the NGL renderer.
   • nVidia internal tracking Bug #5382305

GNOME/GTK Application tooltips are stretched/distorted

Original thread - (GeForce RTX 4070) GTK application issue with NVIDIA GPU. GNOME Bug report - Tooltips are stretched (#5832) Reposting the thread with a more descriptive title for additional clarity/discoverability. In GTK applications, some menus and tooltips become stretched/improperly sized. Have personally seen this issue crop up in GNOME Software dropdown menus and hover tooltips in any GTK applications. It’s especially apparent in GNOME Builder (IDE) with auto-completion. A couple exa…

3. GTK4 apps background CPU usage with the Vulkan backend renderer.
   • nVidia internal tracking Bug #5236115 (/proc/stat) (appears resolved)
   • nVidia internal tracking Bug #5238502 (futex) (bigger issue)

[560.35.03] GTK4 apps background CPU usage with Vulkan renderer

Originally filed against the GTK project: GTK4 apps background CPU usage high with Vulkan renderer (#7117) · Issues · GNOME / gtk · GitLab This was quickly identified as an nVidia driver issue. As of gtk 4.16 the Vulkan rendering backend is used by default. GTK4 apps are consuming unexpected CPU cycles while idle in the background when using the Vulkan backend. This does not occur with the NGL renderer. Steps to reproduce Launch a GTK4 app (e.g. GTK4-demo, Nautilus, gnome-text-editor) us…

4. Nvidia framebuffer driver isn’t compatible with simpledrm so boot output and TTYs are blank
   • nVidia internal tracking Bug #4157529 (partially resolved in 580 upcoming driver)

Nvidia driver isn't compatible with simpledrm so boot output and TTYs are blank

Hi, I run Fedora 37 and using nvidia proprietary drivers I cannot access any of my TTYs, and the kernel out during boot (disabling rghb quiet in grub) is blank once the driver gets loaded. As far as I can tell, this was caused by a change in Fedora 36 where fbdev (drivers?) were replaced with CONFIG_DRM and CONFIG_SYSFB_SIMPLEFB. On my gentoo install running the latest nvidia drivers, I can run CONFIG_FB_SIMPLE on my kernel (which I can’t on Fedora because it’s prebuilt) without an issue and I …

Current software stack:

• kernel 6.15.5
• wlroots 0.19
• sway 1.11 (Native Wayland)
• gtk4 4.18.6 (-Dx11-backend=false)
• vulkan-icd-loader 1.4.313
• nVidia 575.64.03
  
  

I will continue to update this tracking thread for each successive driver release.