Bug 1759285 - Touchpad vertical sensitivity is higher than horizontal sensitivity
Summary: Touchpad vertical sensitivity is higher than horizontal sensitivity
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libinput
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-07 18:32 UTC by ali.sherif10
Modified: 2020-05-26 18:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:07:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ali.sherif10 2019-10-07 18:32:51 UTC
Description of problem:
After installing Fedora 30, I found that vertical sensitivity is much higher than horizontal sensitivity.

Version-Release number: 1.14.1.

How reproducible:
Always, because I got it in Kubuntu 19.04 too.

Steps to Reproduce:
1. Install Fedora 30.

Actual results:
Vertical sensitivity is higher than horizontal sensitivity and moving the cursor horizontally is slow.

Expected results:
Vertical and horizontal touchpad speeds are proper.

Additional info:
Laptop: HP Pavilion g6.
I didn't have the problem in previous versions of distributions. I don't know exactly when it started.

Comment 1 Peter Hutterer 2019-10-13 22:54:32 UTC
please run the touchpad-edge-detector tool from the libevdev-utils package and post the output here, thanks.

Comment 2 ali.sherif10 2019-10-17 18:32:42 UTC
How to use it? Sorry.
I tried:
$ sudo touchpad-edge-detector 40x60 /dev/input/event0
$ sudo touchpad-edge-detector 40x60 /dev/input/event1
The output was:
Error: this device does not have abs axes

I chose the size inaccurately.

Comment 3 Peter Hutterer 2019-10-17 21:07:50 UTC
you'll need to run it against the correct event node, run libinput record (libinput-utils.rpm) without arguments, it'll give you a list of devices. Pick your touchpad from that list. Note that you may have 2 touchpad kernel devices, only one of which will send events. So while libinput record is running, touch the device - if you see events scroll past that's the right event node.

Once you identified the device node, use that same event node for the touchpad-edge-detector

Comment 4 ali.sherif10 2020-01-08 12:38:24 UTC
I apologize for the late reply.
After either installing Fedora 31 or installing it followed by some updates, the problem seems to be fixed.

$ sudo touchpad-edge-detector 40x60 /dev/input/event4
Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event4
Move one finger around the touchpad to detect the actual edges
Kernel says:	x [1222..5734], y [910..4974]
Touchpad sends:	x [2970..4853], y [1948..4009] |^C

Touchpad size as listed by the kernel: 94x42mm
User-specified touchpad size: 40x60mm
Calculated ranges: 1883/2061

Suggested udev rule:
# <Laptop model description goes here>
evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0885120000005D10000600000:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:*
 EVDEV_ABS_00=2970:4853:47
 EVDEV_ABS_01=1948:4009:34
 EVDEV_ABS_35=2970:4853:47
 EVDEV_ABS_36=1948:4009:34

Comment 5 ali.sherif10 2020-01-08 12:39:12 UTC
Recently, touchpad movement is slow, before login to account only.

Comment 6 Peter Hutterer 2020-01-08 22:52:36 UTC
There is a hwdb entry in systemd for the Paviliong6, but that seems to be a different device than what you have. To fix this, find the 60-evdev.hwdb file on your system, it has the instructions on what to do with this snippet. You can shorten the lookup rule a bit so you end up with this:

evdev:name:SynPS/2 Synaptics TouchPad:dmi:*svnHewlett-Packard:pnHPPaviliong6NotebookPC:*
 EVDEV_ABS_00=2970:4853:47
 EVDEV_ABS_01=1948:4009:34
 EVDEV_ABS_35=2970:4853:47
 EVDEV_ABS_36=1948:4009:34


This should take care of any pointer movement issues. Ideally you can submit this to systemd upstream as a PR, the 60-evdev.hwdb file has instructions for that too.

Comment 7 Ben Cotton 2020-04-30 20:34:19 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-05-26 18:07:49 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.