[Bug 53572] New: Misbehaving system tray icons on Wayland session

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53572

Bug ID: 53572
           Summary: Misbehaving system tray icons on Wayland session
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

This is a bit more complex to explain, as this happens more specifically if you
are on a Wayland session desktop. May be a duplicate of 48550 but I decided to
drop more of what I could find out.

Previously this was reported on KDE's Bugzilla as well and currently there may
not be an easy fix on Plasma's side for a number of reasons. First, it may be
using a deprecated proxy, XEmbedSNIProxy, which may be supported in X11 in a
"very hacky way" as described in the bug report and it is completely
unsupported in Wayland. Other apps also have this issue, like Anydesk, but Wine
may be used for a lot more so it is more common to see those around.

What happens is that, while the icon may appear on the tray, the "interactible"
part of the icon is usually on the top left corner of the screen. And if there
are many tray icons, only one can be interacted with. The icon itself on the
tray is completely static and cannot be interacted with.

Gnome does not have a system tray by default, requiring the user to install one
through extensions. Every other desktop environment, however, does have a
native system tray. Currently, KDE Plasma in the Wayland session is where this
issue can be replicated, although I imagine other Wayland implementations such
as Sway may also work.

There is a known workaround but it is not perfect. Essentially involves
terminating the XEmbedSNIProxy process and bringing the tray icons from there
into a window with the wmsystemtray command. It is very hacky and far from
ideal. If something can be done on Wine's side to try sorting this out, it
would greatly improve its usability on Wayland, even without a native Wayland
driver. Perhaps a new proxy that works both on X11 and Wayland can replace this
old one?