Re: Vnc for remote display?
Hi Pekka, Thank you for that explanation. I found this post: https://bbs.archlinux.org/viewtopic.php?id=191555 which uses XRandR and i found this quite interesting and was wondering if there's something similar in wayland too that would be independent of the Window manager I choose to use. I'll dig a bit deeper and see what I can find out. Thanks in any case! stdcerr On Thu, Oct 3, 2019 at 6:53 AM Pekka Paalanen wrote: > On Wed, 2 Oct 2019 08:21:26 -0700 > stdcerr wrote: > > > Hi, > > > > I'm very new to Wayland but had this idea: > > Does Wayland support the addition of a non existent monitor? I'm thinking > > that it would be great if one had the ability to add en extra screen and > > directly hook it up to a vnc server so that an extra screen could be > > presented by connecting a vnc client... > > > > Is there an option for this? How is it be configured? > > Hi, > > Wayland has nothing to do to support for that. Such non-existent > monitors are completely up to the display server implementation > instead. All configuration is also up to each display server on its > own, as are their implemented features. > > GNOME desktop has a remoting solution, but I don't know if it supports > virtual monitors aside from cloning physical monitors. I would assume > KDE has something too, and others, but I don't know about them. > > Weston can do several things: it can act as a background RDP desktop > server (not using any physical inputs or outputs), and it can remote > physical outputs via RDP. It can also have virtual outputs via a > GStreamer pipeline or Pipewire. > > You'll have to pick the display server or the desktop environment you > want to work with before a question of configuration can be answered. > > > Thanks, > pq > ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Libinput-touch screen detection
Hi Peter, I modified ID_SEAT to seat0, but it didn't help. Also tried
removing ENV{ID_SEAT} no difference.
Thanks & Best Regards,Sanjay
On Thursday, 3 October, 2019, 12:50:54 pm GMT+1, Peter Hutterer
wrote:
On Thu, Oct 03, 2019 at 10:52:41AM +, sanjay anvekar wrote:
> Hi Peter, I couldn't get reason for missing ID_INPUT_TOUCHSCREEN , my
>udev rule looks as below.
> SUBSYSTEM=="input" KERNEL=="event[0-9]" ENV{ID_INPUT_TOUCHSCREEN}=="1"
> ENV{ID_SEAT}="seat1" SYMLINK+="/dev/input/event0"
you assign seat1 here but libinput by default uses seat0. so the device will
simply be ignored unless you tell libinput to listen to events from seat1.
libinput debug-events --seat seat1 should show the events, and likewise your
compositor provided it listens to the right seat.
>
> I don't have libinput record tool, instead tried with evtest and I see
> BTN_TOUCH, below is capture from evtest
> ~# evtestNo device specified, trying to scan all of
> /dev/input/event*Available devices:/dev/input/event0:
> touchscreen/dev/input/event1: Dell Dell USB Optical MouseSelect the
> device event number [0-1]: 0Input driver version is 1.0.1Input device ID: bus
> 0x18 vendor 0x0 product 0x0 version 0x0Input device name:
> "touchscreen"Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY)
> Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 48
> (ABS_MT_TOUCH_MAJOR) Value 0 Min 0 Max 600
> Event code 53 (ABS_MT_POSITION_X) Value 0 Min 168
> Max 3908 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min
> 195 Max 4045Properties:Testing ... (interrupt to exit)Event:
> time 1569995436.407176, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1Event:
> time 1569995436.407176, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value
> 96Event: time 1569995436.407176, type 3 (EV_ABS), code 53
> (ABS_MT_POSITION_X), value 630Event: time 1569995436.407176, type 3 (EV_ABS),
> code 54 (ABS_MT_POSITION_Y), value 693Event: time 1569995436.407176,
> ++ SYN_MT_REPORT Event: time 1569995436.407176,
> -- SYN_REPORT Event: time 1569995436.413546, type 3
> (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 94Event: time
> 1569995436.413546, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value
> 640Event: time 1569995436.413546, type 3 (EV_ABS), code 54
> (ABS_MT_POSITION_Y), value 705Event: time 1569995436.476318, ++
> SYN_MT_REPORT Event: time 1569995436.476318, --
> SYN_REPORT Event: time 1569995436.482637, type 3 (EV_ABS), code
> 48 (ABS_MT_TOUCH_MAJOR), value 85Event: time 1569995436.482637, type 3
> (EV_ABS), code 53 (ABS_MT_POSITION_X), value 645Event: time
> 1569995436.482637, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value
> 696Event: time 1569995436.482637, ++ SYN_MT_REPORT
> Event: time 1569995436.543353, -- SYN_REPORT
> Event: time 1569995436.549449, type 3 (EV_ABS), code 48
> (ABS_MT_TOUCH_MAJOR), value 89Event: time 1569995436.549449, type 3 (EV_ABS),
> code 53 (ABS_MT_POSITION_X), value 638Event: time 1569995436.549449, type 3
> (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 697Event: time
> 1569995436.549449, ++ SYN_MT_REPORT Event: time
> 1569995436.549449, -- SYN_REPORT Event: time
> 1569995436.27, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value
> 102Event: time 1569995436.27, type 3 (EV_ABS), code 53
> (ABS_MT_POSITION_X), value 638Event: time 1569995436.27, type 3 (EV_ABS),
> code 54 (ABS_MT_POSITION_Y), value 709Event: time 1569995436.27,
> ++ SYN_MT_REPORT Event: time 1569995436.27,
> -- SYN_REPORT Event: time 1569995436.752071, type 1
> (EV_KEY), code 330 (BTN_TOUCH), value 0Event: time 1569995436.752071, type 3
> (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 0Event: time 1569995436.752071,
> ++ SYN_MT_REPORT Event: time 1569995436.752071,
> -- SYN_REPORT
impossible to read, sorry.
Cheers,
Peter
>
> Does this indicate that Kernel driver is working fine and issue is with some
> configuration ? Please let me know.
> Thanks & Best Regards,Sanjay
>
> On Wednesday, 2 October, 2019, 07:16:32 pm GMT+1, Peter Hutterer
> wrote:
>
> On Wed, Oct 02, 2019 at 04:40:24PM +, sanjay anvekar wrote:
> > Hi Peter, Thank you for your response. I tried changing udev properties
> >but it didn't help. Here is output from udevadm command.udevadm info
> >/dev/input/event0P:
> >/devices/soc0/soc/210.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0N:
> > input/event0S: input/by-path/platform-21a4000.i2c-eventE:
> >DEVLINKS=/dev/input/by-path/platform-21a4000.i2c-eventE:
> >DEVNAME=/dev/input/event0E:
>
Re: libinput drops keys from infrared remotes after changing keymap
On Tue, Oct 01, 2019 at 09:39:51AM +0100, Sean Young wrote: > Hi Hans, > > On Mon, Sep 30, 2019 at 01:29:59PM +0200, Hans de Goede wrote: > > On 30-09-2019 10:33, Sean Young wrote: > > > On Mon, Sep 30, 2019 at 11:34:04AM +1000, Peter Hutterer wrote: > > > > On Sun, Sep 29, 2019 at 08:17:38PM +0100, Sean Young wrote: > > > > > Any thoughts on this would be appreciated! > > > > > > > > libinput relies on udev, either directly or through the X server. So if > > > > you > > > > trigger your device to get removed and re-added through udev, libinput > > > > will > > > > add it and re-initialize it with whatever current bits it has. > > > > > > > > sudo udevadm trigger --action=remove /sys/class/input/event5 > > > > sudo udevadm trigger --action=add /sys/class/input/event5 > > > > > > Hmm, this is bit of an ugly workaround, even if generated them from > > > ir-keytable. > > > > > > We could change the kernel to re-create the input device when the keymap > > > changes, but this does not fit the current model very well. > > > > > > Not quite sure how to solve this yet. > > > > Just reading along here as an ex libinput contributor. I have the feeling > > that it will help if you can explain your specific use-case, because it > > sounds like you really want to change the keymap on the fly, while normally > > the keymap is something which gets setup once and the loaded by udev add > > device init time... > > You're absolutely right, that is exactly what I'm trying to do. > > > So can you please explain your specific use-case here? > > Simply loading a new keymap while logged in, or rather solve the issue of > "my remote doesn't work after loading the correct keymap". > > My longer term goal is to provide gnome-control-center plugin for > configuring IR receivers. > > So what I'm hearing is that from libinput's perspective, an input device > should not change once created. In order to support this use-case, either > ask the user to logout/login or the kernel should re-create the input > device when the keymap changes. just a late addition here: libinput devices are (currently) static too, so libinput callers don't expect them to change. this may or may not be a problem, depending on the caller. e.g. the ones calling libinput_device_keyboard_has_key() wouldn't expect that to change during the lifetime of the device. so even if we'd move the key mappings above a few layers, we'd still end up with the virtual device removal/addition. Cheers, Peter ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Vnc for remote display?
On Wed, 2 Oct 2019 08:21:26 -0700 stdcerr wrote: > Hi, > > I'm very new to Wayland but had this idea: > Does Wayland support the addition of a non existent monitor? I'm thinking > that it would be great if one had the ability to add en extra screen and > directly hook it up to a vnc server so that an extra screen could be > presented by connecting a vnc client... > > Is there an option for this? How is it be configured? Hi, Wayland has nothing to do to support for that. Such non-existent monitors are completely up to the display server implementation instead. All configuration is also up to each display server on its own, as are their implemented features. GNOME desktop has a remoting solution, but I don't know if it supports virtual monitors aside from cloning physical monitors. I would assume KDE has something too, and others, but I don't know about them. Weston can do several things: it can act as a background RDP desktop server (not using any physical inputs or outputs), and it can remote physical outputs via RDP. It can also have virtual outputs via a GStreamer pipeline or Pipewire. You'll have to pick the display server or the desktop environment you want to work with before a question of configuration can be answered. Thanks, pq pgp4w_nagPnRG.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Vnc for remote display?
Hi, I'm very new to Wayland but had this idea: Does Wayland support the addition of a non existent monitor? I'm thinking that it would be great if one had the ability to add en extra screen and directly hook it up to a vnc server so that an extra screen could be presented by connecting a vnc client... Is there an option for this? How is it be configured? Thanks, Stdcerr ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Libinput-touch screen detection
On Thu, Oct 03, 2019 at 10:52:41AM +, sanjay anvekar wrote:
> Hi Peter, I couldn't get reason for missing ID_INPUT_TOUCHSCREEN , my
> udev rule looks as below.
> SUBSYSTEM=="input" KERNEL=="event[0-9]" ENV{ID_INPUT_TOUCHSCREEN}=="1"
> ENV{ID_SEAT}="seat1" SYMLINK+="/dev/input/event0"
you assign seat1 here but libinput by default uses seat0. so the device will
simply be ignored unless you tell libinput to listen to events from seat1.
libinput debug-events --seat seat1 should show the events, and likewise your
compositor provided it listens to the right seat.
>
> I don't have libinput record tool, instead tried with evtest and I see
> BTN_TOUCH, below is capture from evtest
> ~# evtestNo device specified, trying to scan all of
> /dev/input/event*Available devices:/dev/input/event0:
> touchscreen/dev/input/event1: Dell Dell USB Optical MouseSelect the
> device event number [0-1]: 0Input driver version is 1.0.1Input device ID: bus
> 0x18 vendor 0x0 product 0x0 version 0x0Input device name:
> "touchscreen"Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY)
> Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 48
> (ABS_MT_TOUCH_MAJOR) Value 0 Min 0 Max 600
> Event code 53 (ABS_MT_POSITION_X) Value 0 Min 168
> Max 3908 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min
> 195 Max 4045Properties:Testing ... (interrupt to exit)Event:
> time 1569995436.407176, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1Event:
> time 1569995436.407176, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value
> 96Event: time 1569995436.407176, type 3 (EV_ABS), code 53
> (ABS_MT_POSITION_X), value 630Event: time 1569995436.407176, type 3 (EV_ABS),
> code 54 (ABS_MT_POSITION_Y), value 693Event: time 1569995436.407176,
> ++ SYN_MT_REPORT Event: time 1569995436.407176,
> -- SYN_REPORT Event: time 1569995436.413546, type 3
> (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 94Event: time
> 1569995436.413546, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value
> 640Event: time 1569995436.413546, type 3 (EV_ABS), code 54
> (ABS_MT_POSITION_Y), value 705Event: time 1569995436.476318, ++
> SYN_MT_REPORT Event: time 1569995436.476318, --
> SYN_REPORT Event: time 1569995436.482637, type 3 (EV_ABS), code
> 48 (ABS_MT_TOUCH_MAJOR), value 85Event: time 1569995436.482637, type 3
> (EV_ABS), code 53 (ABS_MT_POSITION_X), value 645Event: time
> 1569995436.482637, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value
> 696Event: time 1569995436.482637, ++ SYN_MT_REPORT
> Event: time 1569995436.543353, -- SYN_REPORT
> Event: time 1569995436.549449, type 3 (EV_ABS), code 48
> (ABS_MT_TOUCH_MAJOR), value 89Event: time 1569995436.549449, type 3 (EV_ABS),
> code 53 (ABS_MT_POSITION_X), value 638Event: time 1569995436.549449, type 3
> (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 697Event: time
> 1569995436.549449, ++ SYN_MT_REPORT Event: time
> 1569995436.549449, -- SYN_REPORT Event: time
> 1569995436.27, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value
> 102Event: time 1569995436.27, type 3 (EV_ABS), code 53
> (ABS_MT_POSITION_X), value 638Event: time 1569995436.27, type 3 (EV_ABS),
> code 54 (ABS_MT_POSITION_Y), value 709Event: time 1569995436.27,
> ++ SYN_MT_REPORT Event: time 1569995436.27,
> -- SYN_REPORT Event: time 1569995436.752071, type 1
> (EV_KEY), code 330 (BTN_TOUCH), value 0Event: time 1569995436.752071, type 3
> (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 0Event: time 1569995436.752071,
> ++ SYN_MT_REPORT Event: time 1569995436.752071,
> -- SYN_REPORT
impossible to read, sorry.
Cheers,
Peter
>
> Does this indicate that Kernel driver is working fine and issue is with some
> configuration ? Please let me know.
> Thanks & Best Regards,Sanjay
>
> On Wednesday, 2 October, 2019, 07:16:32 pm GMT+1, Peter Hutterer
> wrote:
>
> On Wed, Oct 02, 2019 at 04:40:24PM +, sanjay anvekar wrote:
> > Hi Peter, Thank you for your response. I tried changing udev properties
> >but it didn't help. Here is output from udevadm command.udevadm info
> >/dev/input/event0P:
> >/devices/soc0/soc/210.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0N:
> > input/event0S: input/by-path/platform-21a4000.i2c-eventE:
> >DEVLINKS=/dev/input/by-path/platform-21a4000.i2c-eventE:
> >DEVNAME=/dev/input/event0E:
> >DEVPATH=/devices/soc0/soc/210.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0E:
> > ID_INPUT=1E: ID_PATH=platform-21a4000.i2cE:
> >ID_PATH_TAG=platform-21a4000_i2cE: MAJOR=13E: MINOR=64E: SUBSYSTEM=inputE:
> >USEC_INITIALIZED=2341962
>
Re: Libinput-touch screen detection
Hi Peter, I couldn't get reason for missing ID_INPUT_TOUCHSCREEN , my udev
rule looks as below.
SUBSYSTEM=="input" KERNEL=="event[0-9]" ENV{ID_INPUT_TOUCHSCREEN}=="1"
ENV{ID_SEAT}="seat1" SYMLINK+="/dev/input/event0"
I don't have libinput record tool, instead tried with evtest and I see
BTN_TOUCH, below is capture from evtest
~# evtestNo device specified, trying to scan all of /dev/input/event*Available
devices:/dev/input/event0: touchscreen/dev/input/event1: Dell Dell
USB Optical MouseSelect the device event number [0-1]: 0Input driver version is
1.0.1Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0Input device
name: "touchscreen"Supported events: Event type 0 (EV_SYN) Event type 1
(EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 48
(ABS_MT_TOUCH_MAJOR) Value 0 Min 0 Max 600
Event code 53 (ABS_MT_POSITION_X) Value 0 Min 168 Max
3908 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min
195 Max 4045Properties:Testing ... (interrupt to exit)Event: time
1569995436.407176, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1Event: time
1569995436.407176, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value
96Event: time 1569995436.407176, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X),
value 630Event: time 1569995436.407176, type 3 (EV_ABS), code 54
(ABS_MT_POSITION_Y), value 693Event: time 1569995436.407176, ++
SYN_MT_REPORT Event: time 1569995436.407176, --
SYN_REPORT Event: time 1569995436.413546, type 3 (EV_ABS), code 48
(ABS_MT_TOUCH_MAJOR), value 94Event: time 1569995436.413546, type 3 (EV_ABS),
code 53 (ABS_MT_POSITION_X), value 640Event: time 1569995436.413546, type 3
(EV_ABS), code 54 (ABS_MT_POSITION_Y), value 705Event: time 1569995436.476318,
++ SYN_MT_REPORT Event: time 1569995436.476318,
-- SYN_REPORT Event: time 1569995436.482637, type 3
(EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 85Event: time 1569995436.482637,
type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 645Event: time
1569995436.482637, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value
696Event: time 1569995436.482637, ++ SYN_MT_REPORT
Event: time 1569995436.543353, -- SYN_REPORT
Event: time 1569995436.549449, type 3 (EV_ABS), code 48
(ABS_MT_TOUCH_MAJOR), value 89Event: time 1569995436.549449, type 3 (EV_ABS),
code 53 (ABS_MT_POSITION_X), value 638Event: time 1569995436.549449, type 3
(EV_ABS), code 54 (ABS_MT_POSITION_Y), value 697Event: time 1569995436.549449,
++ SYN_MT_REPORT Event: time 1569995436.549449,
-- SYN_REPORT Event: time 1569995436.27, type 3
(EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 102Event: time 1569995436.27,
type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 638Event: time
1569995436.27, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value
709Event: time 1569995436.27, ++ SYN_MT_REPORT
Event: time 1569995436.27, -- SYN_REPORT
Event: time 1569995436.752071, type 1 (EV_KEY), code 330
(BTN_TOUCH), value 0Event: time 1569995436.752071, type 3 (EV_ABS), code 48
(ABS_MT_TOUCH_MAJOR), value 0Event: time 1569995436.752071, ++
SYN_MT_REPORT Event: time 1569995436.752071, --
SYN_REPORT
Does this indicate that Kernel driver is working fine and issue is with some
configuration ? Please let me know.
Thanks & Best Regards,Sanjay
On Wednesday, 2 October, 2019, 07:16:32 pm GMT+1, Peter Hutterer
wrote:
On Wed, Oct 02, 2019 at 04:40:24PM +, sanjay anvekar wrote:
> Hi Peter, Thank you for your response. I tried changing udev properties
>but it didn't help. Here is output from udevadm command.udevadm info
>/dev/input/event0P:
>/devices/soc0/soc/210.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0N:
> input/event0S: input/by-path/platform-21a4000.i2c-eventE:
>DEVLINKS=/dev/input/by-path/platform-21a4000.i2c-eventE:
>DEVNAME=/dev/input/event0E:
>DEVPATH=/devices/soc0/soc/210.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0/event0E:
> ID_INPUT=1E: ID_PATH=platform-21a4000.i2cE:
>ID_PATH_TAG=platform-21a4000_i2cE: MAJOR=13E: MINOR=64E: SUBSYSTEM=inputE:
>USEC_INITIALIZED=2341962
>
> Also tried with 'libinput-debug-events' and following is
> outputlibinput-debug-events --device /dev/input/event0 --verboseinput device
> 'touchscreen', /dev/input/event0 not tagged as input devicefailed to create
> input device '/dev/input/event0'.Failed to initialized device
> /dev/input/event0
> I tested this input device with 'evetest' application and it works, but
> doesn't work with libinput.
> How do I debug further and conclude that it is Kernel driver issue ? Please
> let me know.
> Thanks & Best Regards,Sanjay
