Bug 1337857 - Regression i2c Elan touchpad unresponsive tracking
Summary: Regression i2c Elan touchpad unresponsive tracking
Keywords:
Status: CLOSED DUPLICATE of bug 1335249
Alias: None
Product: Fedora
Classification: Fedora
Component: libinput
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-20 09:25 UTC by Richard Chan
Modified: 2016-05-21 09:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-21 09:27:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Richard Chan 2016-05-20 09:25:38 UTC 
Description of problem:
After upgrade to Fedora 24 beta, i2c Elan touchpad is unreponsive to tracking. It tracks a short distance, is slow and jerky.

Clicks and two finger scrolling work.

Regression from Fedora 23.


Version-Release number of selected component (if applicable):
kernel-4.5.4-300.fc24.x86_64
libinput-1.3.0-1.fc24.x86_64
[    0.932811] i2c /dev entries driver
[    4.075384] input: Elan Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-ELAN0100:00/input/input12


How reproducible:
Always


Steps to Reproduce:
1. Upgrade from Fedora 23 to Fedora 24 beta
2.
3.

Actual results:
Touchpad cannot track finger movement precisely. 
The pointer moves a short distance and stops.

Clicking works
Two finger scrolling works


Expected results:
Touchpad behaves normally.


Additional info:
Was working fine under Fedora 23
Comment 1 Richard Chan 2016-05-21 09:22:52 UTC 
This is Asus Zenbook UX305

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: American Megatrends Inc.
	Version: UX305UA.201
Comment 2 Richard Chan 2016-05-21 09:25:20 UTC 
The fix in  libinput-1.3.0-2.fc24.x86_64

has resolved the issue for me.
Comment 3 Richard Chan 2016-05-21 09:27:24 UTC 

*** This bug has been marked as a duplicate of bug 1335249 ***
Note You need to log in before you can comment on or make changes to this bug.