https://bugs.freedesktop.org/show_bug.cgi?id=99777
--- Comment #12 from Peter Hutterer <[email protected]> ---
(In reply to Nate Graham from comment #11)
> That's odd, because evemu-record is definitely able to see lid switch events
> if I target event0:
yes, that's expected. the kernel's handling is independent of libinput,
libinput may choose not to handle certain devices. fwiw, what evemu sees is the
same that libinput sees.
> Also, `udevadm info` shows stuff:
ID_INPUT_SWITCH is missing, that's the one thing we care about for the switch
code. For other touchpads we use ID_INPUT_TOUCHPAD, etc.
> So... what's going on here?
honestly, no idea at this point. Leave libinput-debug-events running and see
what happens when the touchpad disables itself. Or check the Xorg.log when this
happens to see if there's anything of use.
if you leave libinput-debug-events running, I recommend applying this patch
first:
https://lists.freedesktop.org/archives/wayland-devel/2017-February/033065.html
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
