[libinput] A query regaring key remap functionality

Dear all, I have a query regarding key remap functionality. As of now, there is no key remap functionality provided by libinput. I’m thinking of having key remap functionality in libinput as one of the existing device configuration features. (Actually, I made a patch for libinput already and te

[PATCH wayland v4] server: Add a socket with an existing fd

This adds functionality to allow system-level control over handing out file descriptors for sockets, to allow tighter security when running a Wayland compositor under a Wayland session server. Signed-off-by: Bryce Harrington Cc: Sung-Jin Park Cc: Sangjin Lee --- v2: + Drop tab corrections +

[PATCH weston] weston-info: display output scale

Fall back to not showing anything as before if we don't have a compositor with wl_output new enough (version 2 or newer). Signed-off-by: Jonny Lamb Reviewed-by: Daniel Stone --- clients/weston-info.c | 32 ++-- 1 file changed, 30 insertions(+), 2 deletions(-) diff -

Re: weston flip a null frame first before start launcher

On Thu, 17 Dec 2015 18:27:48 +0800 zou lan wrote: > Hi pekka & others > > I find weston flip a null frame before start the launcher > weston-desktop-shell. So there is always a black surface flash before the > launcher. That doesn't have the relationship with the animation mode. > I think it's c

Re: [PATCH libinput] evdev: drain any pending evdev events on a device

Hi, On 17-12-15 02:11, Peter Hutterer wrote: open_restricted() doesn't always mean 'open the fd'. When the X server uses systemd-logind, the fd is opened once before PreInit and then kept open across devices being disabled and enabled through the protocol. When the device is re-enabled and libi

weston flip a null frame first before start launcher

Hi pekka & others I find weston flip a null frame before start the launcher weston-desktop-shell. So there is always a black surface flash before the launcher. That doesn't have the relationship with the animation mode. I think it's caused by the code weston_output_init which call the weston_outpu

Re: [Wayland1.5]Issue of weston dump,display 'wayland-0' is gone

On Thu, 17 Dec 2015 08:42:37 + Yang Andy wrote: > Hi Bryce > > In normal case,weston-launch and weston can run correctly. > > In very minority case，this issue occurs in the system startup phase. Hi, sounds like you have a race in your systemd configuration. It could be pretty much anythin

RE: [Wayland1.5]Issue of weston dump,display 'wayland-0' is gone

Hi Bryce In normal case,weston-launch and weston can run correctly. In very minority case，this issue occurs in the system startup phase. So,i want to catch some information about weston coredump in which weston/weston-launch is launched by systmed. Andy > Date: Wed, 16 Dec 2015 19:52:37 -0800

Re: [Wayland1.5]Issue of weston dump,display 'wayland-0' is gone

On Thu, Dec 17, 2015 at 08:01:20AM +, Yang Andy wrote: > Hi Bryce > > Thank you for your reply. > > > Have you tried invoking weston directly, without use of weston-launch? > > I did not change the relationship between weston-launch and weston. > > In our system,there is necessary to run we

RE: [Wayland1.5]Issue of weston dump,display 'wayland-0' is gone

Hi Bryce Thank you for your reply. > Have you tried invoking weston directly, without use of weston-launch? I did not change the relationship between weston-launch and weston. In our system,there is necessary to run weston-launch and weston. Andy > Date: Wed, 16 Dec 2015 19:52:37 -0800 > From