Tooltip distortion on KDE Plasma

Hi - I see that there has been some conversation here already about tooltip distortion on GNOME/GTK applications, and that it seems that interest in pursuing a fix may have been muted because GTK has changed to Vulkan by default, which makes the issue moot?

However, on the latest 565 driver, I (and at least a few others) are still seeing the effects of this on KDE Plasma - 495073 – Tooltip rendering issues when rapidly switching between panel icons - is this an issue that will still be pursued by the folks at Nvidia?

Thanks!
nvidia-bug-report.log.gz (146.7 KB)

2 Likes

Still unfixed as of driver version 570.86.16: 499449 – Hovering over the Application Launcher icon, then an application icon, causes the tooltips to become strangely stretched.

Still happening on 570.133.07

It’s been an issue for quite a while now. Never seen it happen with other GPUS.

For me, changing the backend renderer from automatic (openGL) to Vulkan in KDE Plasma fixes the issue. It is not recommended to change that setting, but I have not noticed any secondary issues from it.

Still happening on Driver Version: 570.153.02

Also, Kdenlive crashes on launch when Vulkan is set as the Qt Quick backend.

Still an issue with 575.57.08 and it’s easy to reproduce. This wasn’t present with RX 5500 XT before I switched to Nvidia.
And like was noted before, changing the rendering backend to Vulkan fixes the issue.

The issue is still present in 575.64.03, I haven’t switched to the Vulkan backend

nvidia-bug-report.log.gz (823.6 KB)

Thanks for the report. I’ve filed NVIDIA internal bug 5382305 for this.

Thanks for filing. One should already exist tho. This is an old issue with a lengthy history.

nVidia developer Erik Kurzinger @ekurzinger was working on a fix for this that was supposed to land on a branch about a year ago.

See here:

And original bug report against GTK here:

I’ll link the new bug number back to the old tracking thread.

Thanks for those pointers. It is possible the fix got lost in the shuffle when Erik went back to school. Or, from the root cause analysis in the GNOME/GTK thread, the bug was pretty specific to the API usage. It is conceivable in the KDE case the API usage is different enough that the fix for the GTK usage doesn’t apply.

Thanks for more of the backstory!

Another data point… I’ve recently switched from Gnome (mutter) to Sway (wlroots ) and this same issue is present with both display servers / compositors.

FWIW both were built as pure native Wayland with no Xwayland support compiled in.