On Wed, Nov 30, 2022 at 03:12:31PM +0200, Vadim Likholetov wrote:
On 30 Nov 2022, at 13:29, Alyssa Ross <alyssa.ross@unikie.com> wrote:
On Wed, Nov 30, 2022 at 12:32:28PM +0200, Vadim Likholetov wrote:
On Wed, Nov 30, 2022 at 12:24 PM Alyssa Ross <alyssa.ross@unikie.com> wrote:
On Wed, Nov 30, 2022 at 12:14:28PM +0200, Vadim Likholetov wrote:
Thank you for the feedback! I managed to make foot terminal working in my setup -- the issue was in lack of compositor ( weston in my case) on the guest, looks like it's the common issue for wayland programs, so now I have competitive advantage over virtio-gpu setup :)
Interesting — why does it need there to be a compositor in the guest? Doesn't Waypipe act as the compositor?
No, why should it? Also wayland-info shows the screen says the display has no compositor.
My understanding of how Waypipe, Sommelier, and wayland-proxy-virtwl work is that they implement the compositor side of the Wayland protocol, and then proxy it to the real compositor running outside of the VM.
Since hello-wayland appears on the host, it must be talking to the host compositor over Waypipe.
It's weird that wayland-info doesn't find a compositor though. I wonder why, when hello-wayland is able to find it.
Stil not sure, even have looked into the code, I think it works one level down, so it requires external compositor. Should check by wayland-info on other ( not waypipe) implementations.
Yeah. I'd also be interested to know if running Weston inside the guest also fixes foot for you with virtio-gpu. My instinct is that it will, since it means Weston is the application running over virtio-gpu, rather than foot.