Wayland severe flickering on RTX 5060 Ti (595-open) when viewing specific images/Matplotlib graphs. No Xid errors.

NVIDIA Open GPU Kernel Modules Version

595.71.05

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Ubuntu 26.04 LTS (Resolute Raccoon)

Kernel Release

7.0.0-15-generic

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

NVIDIA GeForce RTX 5060 Ti (PCI ID: 10de:2d04)

Describe the bug

The screen flickers aggressively under Wayland. The flickering is triggered specifically when viewing certain images (like photos with embedded color profiles in a browser or image viewer) or when opening 2D graphs generated by Python's Matplotlib.

I am forced to use the -open modules because the proprietary modules fail to initialize this GPU on this driver version (RmInitAdapter failed, device minor number 0).

Troubleshooting Steps Taken:

• The issue persists even if I force MUTTER_DEBUG_DISABLE_HW_CURSORS=1, MUTTER_DEBUG_FORCE_KMS_MODE=simple, or disable hardware acceleration in Firefox.
• It ONLY stops if I force software rendering globally for GUI apps (LIBGL_ALWAYS_SOFTWARE=1).
• The nvidia-bug-report log shows NO Xid errors and NO compositor crashes. The driver thinks rendering is perfectly fine.
• This strongly suggests a silent display-pipeline/KMS issue or a temporal dithering conflict over HDMI on Wayland when rendering specific color patterns.

To Reproduce

1. Boot Ubuntu 26.04 (Wayland session) with an RTX 5060 Ti using the 595-open driver branch.
2. Open a Chromium/Firefox browser with hardware acceleration enabled, or open a Python Matplotlib graph (Qt/GTK backend).
3. View an image with specific dark tones/embedded color profiles (e.g., photos on LinkedIn or generated plots).
4. Observe aggressive physical screen flickering/tearing on the monitor.
5. The flickering stops immediately if the application is closed or if hardware acceleration is globally disabled (LIBGL_ALWAYS_SOFTWARE=1).

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report (2).log

More Info

No response

Begin with the attached nvidia-bug-report log and the 595-open Wayland reproduction on the RTX 5060 Ti; compare behavior with hardware acceleration and LIBGL_ALWAYS_SOFTWARE=1 as described. Trace the relevant display/KMS path, then confirm the triggering images and Matplotlib graphs no longer flicker without software rendering.