You can see the tree using the xwininfo command, like this: $ xwininfo -tree -root The root of the tree is called the root window and fills the screen.
#PROBLEMS WITH XQUARTZ WINDOW SIZE WINDOWS#
The X server maintains a tree of windows (rectangles) and the applications manipulate it. Unlike Wayland, where applications are mostly unaware of each other, X is much more collaborative. So instead I'd been using ssh -Y vm from the host to forward X11 connections to the host's Xwayland, Sommelier already has support for this, but it doesn't work for the applications I want to use.įor example, popup menus appear in the center of the screen, text selections don't work, and it generally crashes after a few seconds (often with the error xdg_surface has never been configured).
In fact, I found that doing this avoided several bugs in Sway's built-in Xwayland support. I already had to write a Wayland proxy ( wayland-proxy-virtwl) to run in each VMĪnd relay Wayland messages over virtwl, so I decided to extend it to handle Xwayland too.Īs a bonus, the proxy can also be used even without VMs, avoiding the need for any X11 support in Wayland compositors at all. It wouldn't have any way to ask the compositor to put Xwayland's surfaces into a window frame, because Xwayland is a separate application. We can't have a third-party application act as the X11 window manager. It doesn't work when running applications in VMs,īecause each VM needs its own Xwayland service and existing compositors can only manage one.īecause Wayland (unlike X11) doesn't allow applications to mess with other applications' windows,.
#PROBLEMS WITH XQUARTZ WINDOW SIZE CODE#
In my last post, Qubes-lite with KVM and Wayland, I described setting up a Qubes-inspired Linux system that runs applications in virtual machines.
0 kommentar(er)
