<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - kernel:touchpad left/right clicking no longer being registered" href="https://bugs.freedesktop.org/show_bug.cgi?id=101179#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - kernel:touchpad left/right clicking no longer being registered" href="https://bugs.freedesktop.org/show_bug.cgi?id=101179">bug 101179</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>Bisecting a kernel is easier than you'd expect, at least the basic approach: <a href="https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/bug-bisect.html">https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/bug-bisect.html</a> I suspect the biggest difficulty is figuring out what to do with builds that don''t build but you can do a git bisect skip on those. Plus, there's a high chance you can narrow the bisect to drivers/input, which should only give you a few revisions to look at. Attach an evemu-record of such a sequence though with a broken kernel, that should pinpoint what the problem is, which then may show what the cause could be.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>