Xpra: Ticket #387: wayland server backend

We should be able to plug into wayland and provide remote access for it.

Reading this freerdp implementation, it doesn't look too hard. The main difficulty may be in glueing the C api with our (mostly) python server code.

What makes this now more interesting than before is the availability of sub-surfaces - which would allow us to get YUV data for window's sub-regions (like an embedded video player in a browser), without effort.

Tue, 19 Nov 2013 04:13:56 GMT - Antoine Martin: owner, status, description, milestone changed

Mon, 13 Jul 2015 05:26:08 GMT - rektide: cc set

Tue, 12 Jul 2016 16:51:50 GMT - Antoine Martin: milestone changed

Milestone renamed

Mon, 18 Jul 2016 14:11:13 GMT - Antoine Martin:

More links:

Sun, 21 Aug 2016 09:55:49 GMT - Antoine Martin: milestone changed

Milestone renamed

Mon, 19 Dec 2016 16:54:21 GMT - Antoine Martin:

Recent discussion on wayland-devel with links:

Wed, 15 Feb 2017 10:00:02 GMT - Antoine Martin: milestone changed

Out of time again.

Wed, 20 Sep 2017 06:51:30 GMT - Antoine Martin:

New wiki: Wayland Remoting. It looks nowhere near ready yet.

Wed, 28 Mar 2018 05:11:00 GMT - Antoine Martin: milestone changed

This would also solve #510


Thu, 05 Jul 2018 14:05:31 GMT - Antoine Martin:

Note: it is already possible to use a wayland server as an X11 vfb for xpra. ie: based on ticket:1656#comment:12 with weston:

weston --no-config --socket=wayland-30 &
export WAYLAND_DISPLAY=wayland-30
Xwayland :30 -noreset &
xpra start-desktop :30 --use-display --start=lxsession
xpra attach :30

Thu, 21 Feb 2019 15:21:32 GMT - Antoine Martin:

As per Wayland misconceptions debunked: Things like sending pixel buffers to the compositor are already abstracted on Wayland and a network-backed implementation could be easily made.. I'm not sure it is really that easy: the handling of pixel buffers is just one small part of what we do. The tone of this post is feisty! The problem is that no one seems to really care: all of the people who want network transparency drank the anti-Wayland kool-aid instead of showing up to put the work in. Yes, more work for us. Yay. Rejoice! Anyway, since they're willing to help, it's worth looking into: If you want to implement this, though, we’re here and ready to support you! Drop by the wlroots IRC channel and we’re prepared to help you implement this

Sat, 13 Apr 2019 03:31:51 GMT - Antoine Martin:

For native client support, see #2243.

Tue, 02 Jul 2019 21:30:39 GMT - mviereck: cc changed

Wed, 03 Jul 2019 15:42:48 GMT - Antoine Martin: summary, milestone changed

Thu, 25 Jul 2019 14:14:11 GMT - Antoine Martin:

For keyboard mapping support, see #1049 and ticket:2368#comment:1

Sat, 15 Feb 2020 14:37:01 GMT - Antoine Martin: milestone changed

Wed, 06 May 2020 05:32:32 GMT - Antoine Martin:

The Wayland Protocol.

Sun, 17 May 2020 21:26:36 GMT - comex: cc changed

Thu, 02 Jul 2020 06:04:50 GMT - Antoine Martin:

We're in the same boat as barrier, though there are now virtual device methods? wlroots based VNC server and the protocols it uses virtual_keyboard_unstable_v1 and wlr_virtual_pointer_unstable_v1 (but "unstable" and v1.. been burnt by wayland v1 before)

Sun, 12 Jul 2020 04:58:50 GMT - Antoine Martin:

This is for a secondary virtual screen, but maybe the code to use is the same? wayvnc : Create virtual screen to use as second screen

synergy: wlr-synergy-client.c

Thu, 08 Oct 2020 04:53:33 GMT - Antoine Martin: milestone changed

Sat, 23 Jan 2021 04:53:52 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/387