4 ms·

I think the reason for rootful XWayland to exist, and the fact that it's like 100% made by Red Hat, hints that this is why they are doing it. But I would like

I think the reason for rootful XWayland to exist, and the fact that it's like 100% made by Red Hat, hints that this is why they are doing it. But I would like to run native Wayland clients too, and have them behave in such an environment. Can a compositor be made in such a fashion that it would cooperate with XWayland and manage native clients?

yjftsjthsd-h 3y ago
> I think the reason for rootful XWayland to exist, and the fact that it's like 100% made by Red Hat, hints that this is why they are doing it. I had assumed the same, but then they announced that they were discontinuing xorg-server without pointing to rootful xwayland, so I'm not sure how to read the situation. > But I would like to run native Wayland clients too, and have them behave in such an environment. Can a compositor be made in such a fashion that it would cooperate with XWayland and manage native clients? You can have a mix with non-rootful xwayland on a wayland compositor; that's the easy path, really. I don't know if there's a way to have a X11 window manager control Wayland windows in that kind of system, though.