<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#c10">Comment # 10</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>From the log: input device 'Lid Switch', /dev/input/event0 not tagged as input device not using input device '/dev/input/event0'. So whatever you're seeing is not the result of the new lid switch code, at least not in libinput. For the new lid switch code to work, you'll need a relatively recent systemd patch to tag switch devices with ID_INPUT_SWITCH. Without that, libinput will ignore the device. You can easily verify this with udevadm info /sys/class/input/event0 (for your switch device) and see if that shows up. If not, the new lid code isn't triggered. Coincidentally, the evemu-event command above can verify this, send it with --value 1 to logically close the lid - the touchpad should still work.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>