Xwayland on demand (Re: [PATCH xwayland 3/3] xwayland: Handle the case of windows being realized before redirection)

Pekka Paalanen ppaalanen at gmail.com
Thu Jan 17 09:04:39 UTC 2019


On Thu, 17 Jan 2019 09:47:05 +0100
Olivier Fourdan <ofourdan at redhat.com> wrote:

> Hi,
> 
> On Thu, Jan 17, 2019 at 9:23 AM Pekka Paalanen <ppaalanen at gmail.com> wrote:
> >
> For xrdb specifically, actually, the X11 resources are stored in a
> couple of properties on the root window ("RESOURCE_MANAGER" and
> "SCREEN_RESOURCES") so Xwayland /could/ set those on init, it's more
> the whole logic of merging resources from different files, optionally
> invoking a C preprocessor, etc. that would be painful in Xwayland
> IMHO.
> 
> So if there was a way to (re)use xrdb to send the resources string to
> stdout instead of setting the property itself, Xwayland could possibly
> get values to set the properties and do that on startup before any X11
> client had a chance to connect.
> 
> Maybe that would be simplereasier than having side-channels or
> interlocking in place at startup?

Hi Olivier,

maybe, but that is again a solution to just one specific issue, while I
believe there is a whole category of issues like this. The XWM init is
another.

If someone starts a X11 window manager as the very first X11 client,
could that break the whole Wayland compositor's XWM thing completely?
Do we want to protect against that?

Is it worth to solve the whole category at once? I don't know.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.x.org/archives/xorg-devel/attachments/20190117/0a437c32/attachment.sig>


More information about the xorg-devel mailing list