Tooltip distortion on KDE Plasma

Graphics / Linux Linux
1

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)

3 Likes
2

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.

3

Still happening on 570.133.07

4

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

5

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.

6

Still happening on Driver Version: 570.153.02

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

7

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.

image
image202×105 11.2 KB

8

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)

9

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

1 Like
10

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.

11

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.

12

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.

13

This might be the same problem that GTK4 ran into, where the app tries to resize a window, but the new size doesn’t get applied until the next frame. Erik was working on a driver-side fix for that, but unfortunately, it didn’t pan out.

Instead, we’ve been working on a new Wayland platform library with better resizing behavior (among other improvements). It’s still somewhat experimental, but if anyone wants to try it out, we’ve got it published here:

It should work with any 560 series or later driver.

1 Like
14

Cool. Thanks!

Built and installed egl-wayland2 from git main.

COMMAND   PID       USER  FD   TYPE DEVICE SIZE/OFF    NODE NAME
nautilus 1034 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
brave    1351 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0

It’s loaded and in use. Great that it can coexist with egl-wayland.

I’ll give it some testing. As mentioned in the GTK4 thread:

No change with the tooltips with egl-wayland2 of course.

That’s exactly the symptom

It was downright awful at it’s worst with nautilus 46 & 47 and GTK 4.14 & 4.16

15

It can coexist, but note that there’s also a driver bug where the platform library order got flipped around. It went unnoticed before since there was only ever one library to match, but with two of them now, our current drivers will use 10_nvidia_wayland.json before 09_nvidia_wayland2.json.

We should have that fixed in our next release, but in the meantime, you can set an environment variable to make the driver load one or the other:

__EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES=/usr/share/egl/egl_external_platform.d/09_nvidia_wayland2.json

If you prefer to keep /usr/lib clean, then you can also skip the install step for egl-wayland2, and just point at wherever you compiled it:

__EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES=/path/to/egl-wayland2/src/wayland/09_nvidia_wayland2.json \
    LD_LIBRARY_PATH=/path/to/egl-wayland2/build/src/wayland \
    COMMAND...
16

Thanks for the additional info. I hadn’t noticed any issues, after a day of use.

vkcube is segfaulting as of most recent driver, but I’ll crack a separate thread for that with a backtrace. Unrelated.

I packaged it for my distro, so pacman will keep things straight.

It’s in use by pretty much everything GTK and/or Vulkan backend, including compositor.

COMMAND    PID       USER  FD   TYPE DEVICE SIZE/OFF    NODE NAME
sway       852 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
kgx       1014 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
gnome-tex 1339 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
nautilus  1447 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
evolution 1679 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
WebKitWeb 1758 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
brave     1930 tekstryder mem    REG  259,2    84512 1870808 /usr/lib/libnvidia-egl-wayland2.so.1.0.0

I’ll add the environmental variable regardless.

  • kernel 6.15.6
  • wlroots 0.19 (Vulkan Backend) (-D xwayland=disabled)
  • sway 1.11 (Native Wayland)
  • gtk4 4.18.6 (-Dx11-backend=false)
  • nVidia 575.64.03
  • egl-wayland2 1.00
17

so basically after installing egl-wayland2, and doing the work to make the driver use it, you didn’t notice any more distortion in the tooltips, is that correct?

18

No. This had zero effect on the tooltips. Nor did I expect any.

Happy to continue further discussion over on the relevant GTK thread to keep noise down here.

This one’s a newer duplicate anyhow.

19

Speaking of flipped around, I added…

__EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES=/usr/share/egl/egl_external_platform.d/09_nvidia_wayland2.json

…to my environment, and after restarting, all GTK4 applications are rendered upside-down! 😛


20250710_19h16m37s_grim
20250710_19h16m37s_grim1507×1612 142 KB

That’s a new one. Need to brush up on my headstands.

20

thank you for filing the internal bug