Summary: | Taps often ignored | ||
---|---|---|---|
Product: | Wayland | Reporter: | Paul Johnson <pauljohn> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
scroll.evemu
evemu missed taps evemu missed taps try 2 |
Description
Paul Johnson
2017-06-08 03:55:36 UTC
Two things please: first, try libinput 1.7 or ideally git master so we don't try to debug something that may have been fixed since. Second, run sudo evemu-record --autorestart=3 /dev/input/eventXX [somefile] and try to reproduce. This has the advantage that after 3s of inactivity on the touchpad, it'll start a new recording so we don't have to dig through hundreds of events to figure out what's going on. While it's running, try to reproduce it and whenever you fail to reproduce it, just wait 3 seconds and try again. Once it happens, you can stop and attach the last recording. Possibly related to bug 101435 btw Greets. I built libinput-1.7.2 because I could find Debian packaging code I could understand. Compiles fine, installs easy. I still have the "tap ignored" problem pretty often, it has the symptom like the old synclient in the old days, where there was a timeout on taps after moving the cursor. However, this timeout is not every single time. I have run the event tracker you ask for and it generates lots of files. Neat! But I'm not sure which ones to send you. When the "tap missed" phenomenon happens, I go look in output directory and the last evemu file's name is constantly changing. I send you the second to last one? I'm attaching 2 files which I believe will show a one finger tap that is ignored. Can you point me to instruction on how to read these, so I can see a missed tap for myself? Created attachment 132073 [details]
evemu missed taps
missed one finger tap
Created attachment 132074 [details]
evemu missed taps try 2
Can you see missed tap in here?
Sorry, these files are still too messy, I really need a file with a single tap that's missed, or maybe two or three taps out of which one is missed. Otherwise it takes too long for me to identify even where the bug is. The files are sorted by time, so once you reproduce it, wait a few sec to create new file, then the second-to-last is the one with the data. Try it locally by running sudo evemu-play <file> and hit enter, it should replay the missed tap. But for the files to be useful, you need to pause every two, three taps so that no file has more than 3 taps. When you replay the file, leave libinput-debug-events --verbose --enable-tap running in another terminal, that will show you a button event when the tap was detected. You should be able to verify that the recording you have is the right one and the verbose state should also tell you where in the tap state it's going wrong. closing after 2+ months in needinfo |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.