https://bugs.kde.org/show_bug.cgi?id=424485
--- Comment #75 from Guido <[email protected]> --- (In reply to Erin of Yukis from comment #74) > That’s not going to work for GTK4 and also the entire problem here is that > GTK developers and KWin developers have not agreed on a standard approach > for an application to say: This is my D-Bus name. > > There is a GTK proprietary and a Qt proprietary way to do this and KWin only > implements the Qt one. That’s why global menu works with Qt apps but not GTK > apps. (The other difference is that Qt uses the Canonical DBus-Menu API for > publishing its menus, while GTK uses a simplified GLib DBus API instead, but > GDBus-DBbusMenu-Proxy would take care of that *if* KWin told it which GTK > Wayland application window corresponds to which D-Bus name.) I don't understand your reply. The current situation is as follows: QT apps : the global menu always works (Wayland, XWayland, X11) GTK3/4 apps: the global menu does not work on Wayland, but works on Wayland+Xwayland and on X11. The modified version of appmenu-gtk-module seems to address this Wayland-specific issue and, in some cases, resolves it. My suggestion is to modify appmenu-gtk-module so that it uses the same mechanism now used by Chromium , which correctly exports the menu. -- You are receiving this mail because: You are watching all bug changes.
