Dang it. I wish I could say it’s a new one for me, but I did exactly the same thing with egl-x11. I could’ve sworn I tested that and got it right this time, but apparently not.
Anyway, I fixed the y-invert flag, so it should be right side up now.
1 Like
Ha! Well not to take sides, but top left origin makes more sense to me.
After rebuilding and re-applying the env var…
…the tooltips are displaying correctly with the NGL backend. Wow! Thank you.
I was so quick to celebrate uncorrrupted tooltips I failed to notice some major breakage elsewhere.
GBM platform is no longer initializing with the env var set:
$ eglinfo -B
GBM platform:
eglinfo: eglInitialize failed
Wayland platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 575.64.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 575.64.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 575.64.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
This causes…problems.
EDIT:
Threw more vars in the mix to no avail.
__EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES=/usr/share/egl/egl_external_platform.d/09_nvidia_wayland2.json
__GLX_VENDOR_LIBRARY_NAME=nvidia
GBM_BACKEND=nvidia-drm
I’ll have to leave this disabled for now.
EDIT: I’ll report the issue on the egl-wayland2 GitHub instance rather than clutter this thread further.
Oh, right. __EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES tells the driver to load only the libraries you specify, and GBM is also implemented as a platform library in our driver. So, to keep GBM and xlib/xcb enabled, you’d need to include those, too:
__EGL_EXTERNAL_PLATFORM_CONFIG_FILENAMES=/usr/share/egl/egl_external_platform.d/09_nvidia_wayland2.json:/usr/share/egl/egl_external_platform.d/15_nvidia_gbm.json:/usr/share/egl/egl_external_platform.d/20_nvidia_xcb.json:/usr/share/egl/egl_external_platform.d/20_nvidia_xlib.json
I won’t claim to understand the relationship between GBM and those xlibs, and would never have come up with that myself given I don’t so much as have Xwayland compiled into my compositor haha.
But, you’re right of course…
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 575.64.03
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 575.64.03
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 575.64.03
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
-and-
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
hyprland 25143 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
nautilus 25394 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
brave 25545 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
gnome-cal 26404 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
gnome-cha 26492 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
gnome-tex 26593 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
kgx 26686 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
evolution 26785 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
WebKitWeb 26833 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
gnote 27028 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
papers 27196 tekstryder mem REG 259,2 84512 1838410 /usr/lib/libnvidia-egl-wayland2.so.1.0.0
-and-
Current stack:
- kernel 6.15.6
- hyprland (-DNO_XWAYLAND:STRING=true)
- gtk4 4.18.6 (-Dx11-backend=false)
- egl-wayland2 1.00 (
git main@1229d635) - nVidia 575.64.03
Thanks, again.
FYI, the lack of GBM was crashing WebKit, upon which Evolution is dependent.
15_nvidia_gbm.json is for the library that adds EGL support for GBM.
20_nvidia_xcb.json and 20_nvidia_xlib.json are for EGL+X11 applications using libxcb and libx11, respectively, so if you’re not using XWayland for anything, then they aren’t needed (though they won’t do any harm).
Ah good. I intuited that, but now I’ll give those X-related vars the boot.
Whether I’m on mutter, wlroots, or hyprland, I build them all sans X11 / Xwayland.
The bug with tooltips still exists to this day and is affecting a lot of people. I understand this is not a critical bug but is there any plan to ever actually fix it?
have you read the chat? They’re tracking this bug and when they track the bugs they will fix them
Good grief. It’s already fixed, as noted in this thread.
This issue has nothing to do with KDE and everything to do with GTK4.
This thread is a duplicate of GNOME/GTK Application tooltips are stretched/distorted - #12 by Tekstryder and should be closed as such.
I’ll mark the tracking thread as solved when egl-wayland2 is officially tagged for release.
Currently on git main without issue.
My bad for not reading the thread carefully.
This issue has nothing to do with KDE and everything to do with GTK4
Forgive my ignorance but how does this have “everything to do with GTK4” when this thread was originally started to report that this happens on KDE too and it can be reproduced on a fresh installation of KDE?
If I understand correctly now, this has to do with resizing in egl-wayland and is not strictly related to KDE/QT or GTK?
As far as I can see, this does not translate to “this has everything to do with GTK4”. It seems like, according to the bug report you linked, the implementation in GTK was doing something that is technically allowed by the specs but not handled properly by the driver, and there’s a driver patch to fix it.
This does not make it a GTK problem, nor a KDE problem. If anything, this means that KDE must be doing the same thing in the implementation (that conforms to the specs), since the symptom is exactly the same (tooltips are distorted).
It also means that hopefully the fix will work regardless of the desktop environment.
Anyways, thanks for the links and the context. Looking forward to the release of egl-wayland2.
egl-wayland2 might not be ready for KDE yet. Building it and using it fixes tooltip distortion, but it also breaks window previews in the task manager. Not sure if this is a KDE bug or an NVIDIA bug, but all it does is trade one problem for another. I will report to KDE just in case, especially since their vulkan renderer has the same problem with window previews, even with old egl-wayland, so definitely there is something for them to fix.
It does work on my end without an issue on egl-wayland2 at main@eb31eb3
1 Like
this is fully fixed with drivers 590 and newer using egl-wayland2
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.