Bug 2217176

That's either a toolkit issue or a compositor issue, but definitely not Wayland (which is a set of protocol _definitions_).

From the look of it, I suspect that particular application is using Qt. Can you please confirm which toolkit this is happening with?

As far as I know, this program was written with JUCE.
https://juce.com/


[berci@fedora ~]$ ldd /usr/bin/Waveform12
	linux-vdso.so.1 (0x00007fff7ff97000)
	libatomic.so.1 => /lib64/libatomic.so.1 (0x00007fab6146c000)
	libasound.so.2 => /lib64/libasound.so.2 (0x00007fab6135b000)
	libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007fab6128b000)
	libGL.so.1 => /lib64/libGL.so.1 (0x00007fab61204000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fab611ff000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fab611fa000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fab611f3000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fab61112000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fab610ee000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fab60f10000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fab61495000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fab60efc000)
	libpng16.so.16 => /lib64/libpng16.so.16 (0x00007fab60ec3000)
	libz.so.1 => /lib64/libz.so.1 (0x00007fab60ea7000)
	libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x00007fab60dab000)
	libbrotlidec.so.1 => /lib64/libbrotlidec.so.1 (0x00007fab60d9e000)
	libGLX.so.0 => /lib64/libGLX.so.0 (0x00007fab60d6b000)
	libX11.so.6 => /lib64/libX11.so.6 (0x00007fab60c24000)
	libXext.so.6 => /lib64/libXext.so.6 (0x00007fab60c10000)
	libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007fab60b56000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fab60a0d000)
	libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x00007fab609ec000)
	libbrotlicommon.so.1 => /lib64/libbrotlicommon.so.1 (0x00007fab609c9000)
	libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fab6099e000)
	libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007fab60902000)
	libXau.so.6 => /lib64/libXau.so.6 (0x00007fab608fc000)

But I get errors with Asbru Connection Manager too.
Sometimes the "exit" button not working, and tabs "X" close button malfunctioning too.

https://www.asbru-cm.net/

It is a perl and python application with GTK.

I can reproduce the problem with the dropdown menus in with Tracktion Waveform 12 (I had to register on the website https://www.tracktion.com/ and then download a .deb file and extract it manually to be able to install it on Fedora).

That application is running X11 on top of Xwayland.

The issue is with mutter though, the same works fine in other Wayland compositors such as KDE Plasma, Sway or Weston.

→ Moving to mutter.

Since this is a regression and I can reproduce, I ran a bisection in git and this commit came out:

18be74edeb58d755f7e9647f70e9faf4e4259f21 is the first bad commit
commit 18be74edeb58d755f7e9647f70e9faf4e4259f21
Author: Carlos Garnacho <carlosg>
Date:   Fri Apr 21 21:07:01 2023 +0200

    core: Fix map transitions for X11 windows on Wayland
    
    We are attempting to show windows that do not yet have a
    surface/buffer, this makes GNOME Shell avoid transitions
    for these windows.
    
    Since on Wayland X11 windows are also Wayland surfaces,
    this check is also valid for these, and is thus made more
    generic to also cater for these windows.
    
    Eventually, meta_window_update_visibility() is called
    when the surface gets its buffer, so the window can be
    neatly animated.
    
    Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2611
    Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2975>

 src/core/window.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

This is https://gitlab.gnome.org/GNOME/mutter/-/issues/2820 upstream.

Thank you Olivier!