Remote Desktop with Wayland

Hi there, I want to use Linux at work on my workstation PC but currently I can't. The main reason is lack of useful Remote Desktop access to Linux from outside. By useful Remote Desktop access I mean how it's implemented in Windows. In Windows you can connect to a locally started session and

[PATCH 1/2] libweston: Support autodetection of the current XDG_SEAT

--- libweston/compositor-drm.c | 5 + libweston/compositor-fbdev.c | 5 + 2 files changed, 10 insertions(+) diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c index 10adb463..44b2e448 100644 --- a/libweston/compositor-drm.c +++ b/libweston/compositor-drm.c @@ -3502,8

[PATCH 2/2] Document the new handling of XDG_SEAT

--- compositor/main.c | 2 +- man/weston-drm.man | 7 +-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f8a60e97..f632fc0e 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -563,7 +563,7 @@ usage(int error_code)

Re: [wayland + ILM] proxy wrappers usage of wayland 1.11.0 to 1.9.0

Hi, Am Freitag, den 18.08.2017, 18:35 +0530 schrieb Vikas Patil: > Dear All, > > > I have backported following patches from wayland 1.11.0 to 1.9.0 to > test one crash issue [1] . I am able to backport and start Weston > with > it. Is this valid thing to do? > > >

[PATCH wayland v4] doc: start documenting Xwayland

From: Pekka Paalanen This is a rough intro to what Xwayland is and does, with just one implementation detail so far (Window identification). I paid no attention to formatting details, those can be polished in follow-ups. I just want the prose out. I also just

Re: [RFC wayland-protocols] presentation-time: Add request to subscribe to wl_output presentation timings

Hi Pekka, I have updated the RFC patch with the changes discussed until now. I haven't got any feedback yet from the Chromium team about associating the timing object to wl_surface. I will provide further updates when I get more information. In any case, I think the updated patch is a good basis

[PATCH wayland v2] server: document wl_event_loop and wl_event_source

From: Pekka Paalanen This documents all the public API related to wl_event_loop and wl_event_source objects. Signed-off-by: Pekka Paalanen Reviewed-by: Yong Bakos [Pekka: fixed typos pointed by Yong]

[wayland + ILM] proxy wrappers usage of wayland 1.11.0 to 1.9.0

Dear All, I have backported following patches from wayland 1.11.0 to 1.9.0 to test one crash issue [1] . I am able to backport and start Weston with it. Is this valid thing to do? https://cgit.freedesktop.org/wayland/wayland/commit/?id=6d29c0da3cd168e08187cd204d2314188479c0f1 [client:

Re: [PATCH weston] libweston-desktop/xwayland: Make sure racy surfaces are properly mapped

On Fri, 21 Jul 2017 18:43:41 +0200 Quentin Glidic wrote: > On 5/15/17 4:40 PM, Pekka Paalanen wrote: > > On Mon, 15 May 2017 15:29:29 +0200 > > Quentin Glidic wrote: > > > >> From: Quentin Glidic

Re: [RFC weston 0/9] weston-debug protocol, API, and tool

On Thu, 27 Jul 2017 15:13:22 + "Devadoss, Maniraj (RBEI/ECF3; ADITG/SWG)" wrote: > Hello Pekka, > > Please find my replies. > > > What do you think of the alias idea? > This idea looks good to group the debug scopes. > > > I'm still not sure who or

Re: [PATCH wayland 2/3] scanner: Allow adding a prefix to exported symbols

On Fri, 28 Jul 2017 14:06:23 +0100 Emil Velikov wrote: > On 27 July 2017 at 14:01, Pekka Paalanen wrote: > > On Wed, 26 Jul 2017 16:09:32 +0100 > > Emil Velikov wrote: > > > >> On 25 July 2017 at 10:24, Pekka Paalanen

Re: [PATCH wayland 1/3] Pass input/output files as arguments to wayland-scanner

On Wed, 26 Jul 2017 15:57:19 +0100 Emil Velikov wrote: > On 3 July 2017 at 10:16, Jonas Ådahl wrote: > > When input/output files are passed as arguments to wayland-scanner, > > instead of using stdin/stdout, warning and error messages will contain > >

Re: [PATCH 4/5] build: set the scanner --object-type option

On Fri, 28 Jul 2017 13:23:46 +0100 Emil Velikov wrote: > On 27 July 2017 at 14:36, Pekka Paalanen wrote: > > On Wed, 26 Jul 2017 14:56:20 +0100 > > Emil Velikov wrote: > > > >> From: Emil Velikov

Re: [PATCH 3/5] scanner: introduce --object-type option

On Fri, 28 Jul 2017 13:13:48 +0100 Emil Velikov wrote: > On 27 July 2017 at 14:25, Pekka Paalanen wrote: > > On Wed, 26 Jul 2017 14:56:19 +0100 > > Emil Velikov wrote: > > > >> From: Emil Velikov

Re: [PATCH 2/5] scanner: use tabs for indentation.

On Thu, 27 Jul 2017 16:09:53 +0300 Pekka Paalanen wrote: > On Wed, 26 Jul 2017 14:56:18 +0100 > Emil Velikov wrote: > > > From: Emil Velikov > > > > File uses tabs, barring the few instances fixed with this patch. > >

Re: [PATCH 1/5] scanner: remove unused scanner.mk

On Thu, 27 Jul 2017 16:08:25 +0300 Pekka Paalanen wrote: > On Wed, 26 Jul 2017 14:56:17 +0100 > Emil Velikov wrote: > > > From: Emil Velikov > > > > Nothing in the existing codebase references the file. > > > >

Re: Running multliple fullscreen applications on each of the the DRM connector

On Fri, 28 Jul 2017 08:26:04 -0500 Prabhu S wrote: > Currently I have a DRM modeset master which have multiple (HDMI) connectors. > > I suppose there is a limitation (or security feature) in DRM that only one > user process can be a DRM master and only the master can do

Re: [PATCH wayland] scanner: Add autoconf macro to check for the proper scanner

On Fri, 18 Aug 2017 11:36:17 +0200 Quentin Glidic wrote: > On 8/18/17 11:30 AM, Quentin Glidic wrote: > > From: Quentin Glidic > > > > Projects have been using various ways to check for the wayland-scanner, > > mostly based on their

[RFC libweston] Head-based output configuration API a.k.a clone mode infrastructure

Hi, I started designing output configuration API changes earlier this year to accommodate the addition of clone mode to Weston, and in particular a very specific setup: sharing the DRM CRTC for more than one encoder/connector. That setup is the cheapest clone mode possible, with the

Re: [PATCH wayland] scanner: Add autoconf macro to check for the proper scanner

On 8/18/17 11:30 AM, Quentin Glidic wrote: From: Quentin Glidic Projects have been using various ways to check for the wayland-scanner, mostly based on their developper own use case, and often not allowing others use cases to work without a workaround. Hopefully

[PATCH wayland] scanner: Add autoconf macro to check for the proper scanner

From: Quentin Glidic Projects have been using various ways to check for the wayland-scanner, mostly based on their developper own use case, and often not allowing others use cases to work without a workaround. Hopefully this macro will support all use cases without

Re: Add serial to wl_output::geometry?

Hi, Am Freitag, den 18.08.2017, 10:47 +0300 schrieb Pekka Paalanen: > On Thu, 03 Aug 2017 08:27:06 -0400 > Simon Ser wrote: > > > Hello, > > I'm writing a Wayland client that needs to keep track of screens > > across reboots. I registered a wl_output::geometry event

Re: Add serial to wl_output::geometry?

On Thu, 03 Aug 2017 08:27:06 -0400 Simon Ser wrote: > Hello, > I'm writing a Wayland client that needs to keep track of screens > across reboots. I registered a wl_output::geometry event handler. > This event already has the fields "make" and "model", but is missing >

Re: [RFC wayland-protocols] presentation-time: Add request to subscribe to wl_output presentation timings

On Thu, 17 Aug 2017 17:03:22 +0300 Alexandros Frantzis wrote: > On Thu, Aug 17, 2017 at 11:10:12AM +0300, Pekka Paalanen wrote: > > On Mon, 7 Aug 2017 19:00:40 +0300 > > Alexandros Frantzis wrote: > > > > > The

Re: wl_shm_format documentation

On Thu, 17 Aug 2017 23:20:51 +0200 Fredrik Höglund wrote: > Hi, > > I noticed that the documentation for wl_shm_format doesn't specify whether > formats use premultiplied alpha or not. Is that intentional or an oversight? Hi, I think that's an oversight indeed. I'm actually