Re: Spurious touchpad events with closed LID

2017-06-29 Thread Bastien Nocera
On Thu, 2017-06-29 at 09:31 +0200, Pali Rohár wrote: > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > > > > > > > While policy normally belongs to userspace, I'd argue this is > > > workaround for a hardware bug, and in-

Re: Spurious touchpad events with closed LID

2017-06-29 Thread Pali Rohár
On Thursday 29 June 2017 12:15:00 Pavel Machek wrote: > On Thu 2017-06-29 12:11:12, Pali Rohár wrote: > > On Thursday 29 June 2017 12:08:37 Pavel Machek wrote: > > > Hi! > > > > > > On Thu 2017-06-29 09:31:02, Pali Rohár wrote: > > > > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > >

Re: Spurious touchpad events with closed LID

2017-06-29 Thread Pavel Machek
On Thu 2017-06-29 12:11:12, Pali Rohár wrote: > On Thursday 29 June 2017 12:08:37 Pavel Machek wrote: > > Hi! > > > > On Thu 2017-06-29 09:31:02, Pali Rohár wrote: > > > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > > > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > >

Re: Spurious touchpad events with closed LID

2017-06-29 Thread Pali Rohár
On Thursday 29 June 2017 12:08:37 Pavel Machek wrote: > Hi! > > On Thu 2017-06-29 09:31:02, Pali Rohár wrote: > > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > > > > > > > > While policy normally belongs to userspace,

Re: Spurious touchpad events with closed LID

2017-06-29 Thread Pavel Machek
Hi! On Thu 2017-06-29 09:31:02, Pali Rohár wrote: > On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > > > > > While policy normally belongs to userspace, I'd argue this is > > > workaround for a hardware bug, and in-kernel

Re: Spurious touchpad events with closed LID

2017-06-29 Thread Pali Rohár
On Thursday 29 June 2017 00:44:27 Bastien Nocera wrote: > On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > > > > While policy normally belongs to userspace, I'd argue this is > > workaround for a hardware bug, and in-kernel solution would be > > acceptable. > > > > Anyway, disable attr

Re: Spurious touchpad events with closed LID

2017-06-28 Thread Bastien Nocera
On Wed, 2017-06-28 at 22:15 +0200, Pavel Machek wrote: > > While policy normally belongs to userspace, I'd argue this is > workaround for a hardware bug, and in-kernel solution would be > acceptable. > > Anyway, disable attribute would be nice first step. It's already fixed for those of us on r

Re: Spurious touchpad events with closed LID

2017-06-28 Thread Pavel Machek
Hi! > > > When I'm using dock with external input devices (keyboard + mouse) > > > and LID is closed, I'm getting spurious touchpad events and random > > > mouse clicks and movements. > > > > > > It is because top part of LID is above touchpad and probably > > > generates touch pushes. > > > > >

Re: Spurious touchpad events with closed LID

2017-06-26 Thread Pali Rohár
On Monday 26 June 2017 19:03:12 Dmitry Torokhov wrote: > On Mon, Jun 26, 2017 at 06:54:53PM +0200, Pali Rohár wrote: > > Hi! > > > > When I'm using dock with external input devices (keyboard + mouse) > > and LID is closed, I'm getting spurious touchpad events and random > > mouse clicks and moveme

Re: Spurious touchpad events with closed LID

2017-06-26 Thread Dmitry Torokhov
On Mon, Jun 26, 2017 at 06:54:53PM +0200, Pali Rohár wrote: > Hi! > > When I'm using dock with external input devices (keyboard + mouse) and > LID is closed, I'm getting spurious touchpad events and random mouse > clicks and movements. > > It is because top part of LID is above touchpad and pro

Spurious touchpad events with closed LID

2017-06-26 Thread Pali Rohár
Hi! When I'm using dock with external input devices (keyboard + mouse) and LID is closed, I'm getting spurious touchpad events and random mouse clicks and movements. It is because top part of LID is above touchpad and probably generates touch pushes. Year (or two?) when I had conversation wit