<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Lid switch monitoring occasionally gives false positives, erroneously disabling the internal touchpad"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=99777">99777</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Lid switch monitoring occasionally gives false positives, erroneously disabling the internal touchpad
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Wayland
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>1.5.0
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>blocker
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>libinput
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>pointedstick@zoho.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Hardware: HP Spectre x360 (Kaby Lake, late 2016)
Software: Fedora 25 + GNOME 3.22.2 + libinput 1.6.0-2.fc25

Every since libinput added lid switch support to disable the internal touchpad
(in 1.6.0, I believe), I've had periodic issues with false positives disabling
the touchpad. evemu-record targeting the lid switch shows that what's happening
is that every so often a lid switch closed event is falsely recorded. When this
happens, moving your finger on the touchpad doesn't result in any cursor motion
(confirmed by evemu-record for the touchpad).

Worse, this false state persists across reboots, so when the lid switch is
recorded as closed, rebooting the machine (as you might expect a novice user to
do in a panic) doesn't reset the lid switch value or trigger a re-read, so the
problem does not go away.

Closing and then re-opening the lid to trigger a lid switch change (confirmed
with evemu-record targeting the lid switch) instantly makes the problem
disappear.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>