xpra icon
Bug tracker and wiki

Opened 7 years ago

Last modified 6 days ago

#387 assigned task

wayland server backend

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: minor Milestone: 4.1
Component: server Version:
Keywords: Cc: rektide@…, bachbaum24@…, comex

Description (last modified by Antoine Martin)

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.

Change History (19)

comment:1 Changed 7 years ago by Antoine Martin

Description: modified (diff)
Milestone: future1.0
Owner: changed from Antoine Martin to Antoine Martin
Status: newassigned

comment:2 Changed 5 years ago by rektide

Cc: rektide@… added

comment:3 Changed 4 years ago by Antoine Martin

Milestone: 1.01.1

Milestone renamed

comment:4 Changed 4 years ago by Antoine Martin

More links:

Last edited 4 years ago by Antoine Martin (previous) (diff)

comment:5 Changed 4 years ago by Antoine Martin

Milestone: 1.12.0

Milestone renamed

comment:6 Changed 4 years ago by Antoine Martin

Recent discussion on wayland-devel with links:

comment:7 Changed 3 years ago by Antoine Martin

Milestone: 2.02.1

Out of time again.

comment:9 Changed 3 years ago by Antoine Martin

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

comment:10 Changed 2 years ago by Antoine Martin

Milestone: 2.13.0

This would also solve #510

See:

Last edited 21 months ago by Antoine Martin (previous) (diff)

comment:11 Changed 2 years ago by 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

comment:12 Changed 17 months ago by 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

comment:13 Changed 15 months ago by Antoine Martin

For native client support, see #2243.

comment:14 Changed 12 months ago by mviereck

Cc: bachbaum24@… added

comment:15 Changed 12 months ago by Antoine Martin

Milestone: 3.04.0
Summary: wayland backendwayland server backend

comment:16 Changed 12 months ago by Antoine Martin

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

comment:17 Changed 5 months ago by Antoine Martin

Milestone: 4.04.1

comment:18 Changed 2 months ago by Antoine Martin

comment:19 Changed 7 weeks ago by comex

Cc: comex added

comment:20 Changed 6 days ago by 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)

Note: See TracTickets for help on using tickets.