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
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"
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
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
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
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
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
