| Summary: | Lenovo ThinkPad Yoga 370 touchpad is unresponsive and laggy | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Daniel van Vugt <daniel.van.vugt> |
| Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | peter.hutterer |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://launchpad.net/bugs/1761365 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Daniel van Vugt
2018-04-05 03:51:58 UTC
This bug appears to be fully fixed if I use libinput git master. And half-fixed if I just backport commit ea7498ef to libinput 1.10. What's the policy on marking bugs as fixed? Do you do it when the fix exists in master, or when the fix reaches a release? Once they hit master, they're fixed. Depending on the severity of the bug, how complicated the fix is, where we are in the release cycle and how much time I have they may also hit a stable branch, but often I don't know this myself until I find time to do stable releases. Which I try to do roughly every 2-3 weeks, main releases I think have been every 3 months. But that's more by feel than by fixed schedule too... OK then, marking as fixed. I guess for completeness I should figure out which master commit(s) it was that improved things in the end. Probably the removal of kernel fuzz... |
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.