<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Lid switch monitoring occasionally gives false positives, erroneously disabling the internal touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=99777#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Lid switch monitoring occasionally gives false positives, erroneously disabling the internal touchpad" href="https://bugs.freedesktop.org/show_bug.cgi?id=99777">bug 99777</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>(In reply to Nate Graham from <a href="show_bug.cgi?id=99777#c11">comment #11</a>) > 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: <a href="https://lists.freedesktop.org/archives/wayland-devel/2017-February/033065.html">https://lists.freedesktop.org/archives/wayland-devel/2017-February/033065.html</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>