On 12/29/20 11:26 PM, Samuel Sieb wrote:
More likely what you're really confused about is something that a lot
of people are not aware of. Wayland is a protocol, not a program. I
believe there's a library, but the final implementation is done in
each window manager. The X11 "emulation" is a program called XWayland
that provides an interface layer between the X11 calls and whatever
Wayland implementation is currently running.
Thanks for clarifying; indeed it's the XWayland process that crashes.
I actually support leaving X11 behind---I use wayland myself and I agree
it's the correct evolutionary path for system graphics.
I piped up in this discussion to point out that Wayland has rough
spots. There are many legacy X11 apps still around, some possibly
buggy. They should not crash XWayland in a way that nukes the entire
desktop.
Another problem is the reliability of input streams. The mouse behavior
is realy weird sometimes, as if it was simultaneously losing events and
getting spurious ones.
I suspect that these issues are marginal enough to not affect the
majority of users, which is why they aren't seen as urgent, but I think
they should be addressed for a mainstream Wayland use. I would like to
help debugging that, but it's a complex system and I wasn't able to find
reliable information on how to look inside those issues. For instance, I
understand the separation of layers in X11, and I know how to debug X11
events using xev and such---but I have no idea how to look into why my
mouse clicks in Firefox under Wayland are so weird and unpredictable.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
