Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-03-2019, 05:24 AM
|
#1
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Rep: 
|
Trackpad vertical sensitivity WAY higher than horizontal sensitivity.
I may have posted about this somewhere with a pretty similar title, but I can't find it, and I don't remember it getting anywhere so it doesn't matter.
Currently, I'm on Manjaro with i3-gaps on an HP Pavilion g6 with Linux kernel 5.20.
I've tried a bunch of distros and the only one I remember working is Fedora 29, and only with Plasma.
|
|
|
07-04-2019, 02:29 PM
|
#2
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Welcome to LQ!. A thread discussing the same issue here (in particular post #5 onwards)
https://bbs.archlinux.org/viewtopic.php?id=243305
What you need to know is that there may be a choice of input device drivers available, and the OP in that thread mentions the use of the 'synaptics' Xorg input driver. Wherever possible 'libinput' should now be in use by default, but there may be some hardware that is still better supported by the deprecated 'synaptics' driver. Post #6 contains a solution based on that driver.To complicate matters some desktop environments (in Xorg environment) will only work properly with the the libinput subsystem, and Wayland completely relies on it now.
Please let us know how you get on.
Last edited by ferrari; 07-04-2019 at 02:34 PM.
|
|
|
07-05-2019, 11:32 AM
|
#3
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Original Poster
Rep: 
|
Quote:
Originally Posted by ferrari
Welcome to LQ!. A thread discussing the same issue here (in particular post #5 onwards)
https://bbs.archlinux.org/viewtopic.php?id=243305
What you need to know is that there may be a choice of input device drivers available, and the OP in that thread mentions the use of the 'synaptics' Xorg input driver. Wherever possible 'libinput' should now be in use by default, but there may be some hardware that is still better supported by the deprecated 'synaptics' driver. Post #6 contains a solution based on that driver.To complicate matters some desktop environments (in Xorg environment) will only work properly with the the libinput subsystem, and Wayland completely relies on it now.
Please let us know how you get on.
|
From my understanding, I need the Synaptics driver, right? So when the Manjaro (Architect) installer asked me for X.org related packages, I did pick xf86-input-synaptics. Isn't that the Synaptics driver? And doing the xinput thing from the fifth post, I get "property '121' doesn't exist, you need to specify its type and format".
|
|
|
07-05-2019, 03:25 PM
|
#4
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
To see which input driver is currently in use do
Code:
grep "Using input driver" /var/log/Xorg.0.log
and report back here.
BTW, this will only be applicable if using an Xorg-server, and not Wayland.
Code:
echo $XDG_SESSION_TYPE
Code:
echo $DESKTOP_SESSION
|
|
|
07-06-2019, 05:00 AM
|
#5
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Original Poster
Rep: 
|
There's various stuff for the screen or the power button, probably not important here. It says that for the trackpad, I am using the Synaptics driver.
I'm definitely not on Wayland as well.
|
|
|
07-06-2019, 07:22 AM
|
#6
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Read #6 of the thread I linked to.
|
|
|
07-06-2019, 09:10 AM
|
#7
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Original Poster
Rep: 
|
Quote:
Originally Posted by ferrari
Read #6 of the thread I linked to.
|
Property '148' doesn't exist either.
|
|
|
07-06-2019, 03:54 PM
|
#8
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Run the following to get the device ID for you trackpad
then do
Code:
xinput --list-props <device_ID>
*Use the device _ID pertaining to your trackpad
That will show you the available properties (functions) and their property ID's as well.
When you want to make that permanent, you can use the custom Xorg configuration file as per post #6.
|
|
|
07-07-2019, 05:27 AM
|
#9
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Original Poster
Rep: 
|
Quote:
Originally Posted by ferrari
Run the following to get the device ID for you trackpad
then do
Code:
xinput --list-props <device_ID>
*Use the device _ID pertaining to your trackpad
That will show you the available properties (functions) and their property ID's as well.
When you want to make that permanent, you can use the custom Xorg configuration file as per post #6.
|
Alright so I have a list, and the property Coordinate Transformation Matrix which is currently set to 39, 88 has an ID of 150. So I replaced those commands from the Arch Forum, and this time I get no output, and it doesn't even change anything. Now what?
|
|
|
07-07-2019, 06:44 AM
|
#10
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Which desktop environment is in use? I’m wondering if just using libinput would be better here? (That would require removing the Xorg synaptics package (or at least removing/renaming the synaptics config file).
|
|
|
07-07-2019, 07:47 AM
|
#11
|
Member
Registered: Jul 2019
Distribution: Debian Sid
Posts: 44
Original Poster
Rep: 
|
Quote:
Originally Posted by ferrari
Which desktop environment is in use? I’m wondering if just using libinput would be better here? (That would require removing the Xorg synaptics package (or at least removing/renaming the synaptics config file).
|
I'm using the ratpoison and openbox window managers. And in order to remove the Synaptics driver would I have to reboot? Cause I'm trynna get long uptime
|
|
|
07-07-2019, 01:11 PM
|
#12
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Quote:
And in order to remove the Synaptics driver would I have to reboot?
|
No, you'd just need to restart the X-server (usually CTRL+ALT+Backspace twice).
Instead of removing the synaptics driver package, you could just rename 70-synaptics.conf eg
Code:
sudo mv /etc/X11/xorg.conf.d/70-synaptics.conf /etc/X11/xorg.conf.d/70-synaptics.old
then restart the X-server.
To check if libinput is then in use run the first command given in post #4 again, and check touchpad behaviour again.
|
|
|
All times are GMT -5. The time now is 07:58 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|