Pekka Paalanen wrote:
if you run weston without --xserver, it will never load xwayland.so,
and therefore there will never be the special X window manager, that
will map X window events into Wayland protocol. Therefore you will
never get an X window mapped in Weston.
The special X window manager is implemented in xwayland.so, and for
now, it runs in the same process as Weston.
Is this the intended final design, or will this function be moved to
xserver? It sure seems like it would fit into xserver better. It sounds
to me like the X window events are being somehow encapsulated into the
wayland protocol, so the wayland process can read them and translate
them to real wayland events. Wouldn't this fit much better into the xserver?
Just FYI, that it is intentional to not see any X windows when run like
that. Crashes are a different matter.
Yes the windows do not show up, and the applications appear to work as
though they are waiting for the map event.
Then xwayland.so is running however I get a crash in the interpretation
of window events.
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
