[Bug 291919] x11/nvidia-driver[-devel], x11/nvidia-kmod[-devel], x11/linux-nvidia-libs[-devel], graphics/nvidia-drm*-kmod[-devel], x11/nvidia-settings, x11/nvidia-xconfig: Update to 580.119.02

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291919

Sean Farley <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #4 from Sean Farley <[email protected]> ---
I just upgraded to 580.119.02.  Sadly, this causes a problem if running a
compositor.  I had two xterms open with one on each screen.  After some short
amount of time, moving the cursor in one xterm caused the other to flicker. 
Sometimes, text would act like a VCR blinking 12:00 without any user
interaction.  Supposedly, this also affect 590.48.01.

I found this comment
(https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/950)
on the Nvidia forum:

The Nvidia proprietary driver version 580.119.02 introduced the following
issues when using x11 compositors such as picom with the glx backend.

1. Heavy keyboard input lag in applications such as rofi. The input lag is not
present in google-chrome stable.
2. Application glitching where elements flicker between being rendered and not
rendered, most obvious in virt-manager.
3. Mouse hovering over menus resulting in multiple highlighted elements, often
glitching back and forth between selected elements, when no user input is being
done. Most obvious in virt-manager and sometimes in the thunar right click
context menu when hovering over menu items.

This issue is not present in,

1. Wayland sessions.
2. x11 sessions with the picom backend render set to xrender.
3. x11 sessions with picom compositor disabled.
4. Nvidia driver version 580.105.08

-- 
You are receiving this mail because:
You are on the CC list for the bug.