| Summary: | wayland, "wmctrl -lx" does not list "QEMU" window | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Philippe ROUBACH <philippe.roubach> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | nicolas.fella |
| Priority: | NOR | Keywords: | qt6 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Philippe ROUBACH
2024-03-16 10:44:16 UTC
With X11, I get a window with a title bar with name "QEMU". With Wayland, I get a window without any title bar. Hypothesis : QEMU VM window is a GTK one. Wayland gets some problem to display a GTK window in KDE environment. How to force the window to get a title bar ? wmctrl is an X11-specific tool, it does not work on Wayland. It can list XWayland windows, but not Wayland-native windows Thanks But it's too techie for me. I use Chrome web apps (G contacts, G Calendar, Facebook). The window of these apps are well listed by "wmctrl -lx". I can conclude that : - Chrome window is a XWayland window and not a Wayland native window. - QEMU window is a Wayland native window. Right ? At logging, the script, to launch the vm, needs to detect the QEMU window according to minimize it. Is there a way to workaround the qemu/wmctrl problem ? > Is there a way to workaround the qemu/wmctrl problem ? Write a tool that uses https://wayland.app/protocols/kde-plasma-window-management Thanks I found "wlrctl" https://git.sr.ht/~brocellous/wlrctl I will try it. Today, X11 stays my preferred one. I am not in a hurry to switch to Wayland. |