<div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 25, 2024, 05:08 John Pilkington <<a href="mailto:johnpilk222@gmail.com">johnpilk222@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 24/03/2024 19:56, James Abernathy wrote:<br>
> <br>
> <br>
> On Sun, Mar 24, 2024, 9:16 AM John Pilkington <<a href="mailto:johnpilk222@gmail.com" target="_blank" rel="noreferrer">johnpilk222@gmail.com</a> <br>
> <mailto:<a href="mailto:johnpilk222@gmail.com" target="_blank" rel="noreferrer">johnpilk222@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On my front ends running Wayland I run mythfrontend --platform xcb<br>
> <br>
> Jim A<br>
<br>
Thanks Jim, that could be useful. I just tried the inverse.<br>
<br>
from konsole under Plasma-X11. None of the wayland options were found.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I'm not entirely certain if you expected them to be, but indeed this is certainly not the case. </div><div dir="auto"><br></div><div dir="auto">Wayland is a new architecture that has [partially broken and buggy] backwards compatibility plugins for x11 applications, while x11 is not forward compatible with Wayland protocol applications nor will it ever be. Something like WayDroid does not work under x11 and simply can't.</div><div dir="auto"><br></div><div dir="auto">The fact that QT applications and KDEs compositor can run on both is only due to two completely separate code paths that ideally the developers would like to merge into a Wayland only product.</div><div dir="auto"><br></div><div dir="auto">Mike</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>