Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1816968

Summary: Backport bug fix for P50 touchpads
Product: [Fedora] Fedora Reporter: Jonas Ådahl <jadahl>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-30 20:01:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonas Ådahl 2020-03-25 09:50:28 UTC 
The touchpad on Lenovo P50 is very stuttery and a pain to use.

The following kernel patch fixes the issue:

https://lore.kernel.org/linux-input/20200312031422.GA1823643@jelly/T/

See https://gitlab.freedesktop.org/libinput/libinput/issues/448 as well.
Comment 1 Hans de Goede 2020-03-25 10:30:21 UTC 
The fix for this has been queued up here:

https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/log/?h=for-linus

So it should show up in the next 5.6-rc# without us needing to backport it.
Comment 2 Hans de Goede 2020-03-27 18:44:15 UTC 
The fix for this has landed in Linus' tree, so this should be fixed on the next git-snapshot or rc release of the kernel in F32.
Comment 3 Hans de Goede 2020-03-30 20:01:58 UTC 
As expected an update fixing this is on its way to the updates-testing repo, this issue is being tracked in more detail in bug 1814872, marking this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1814872 ***