Inconsistent device and property labels with xinput
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
On Linux, I use xinput set-prop to enable tapping the touchpad to click. To find the relevant device id as well as property number, I use xinput list-props.
Unfortunately, I find that both the device id and property number are not consistent across sessions. After a reboot, I often need to reconfigure these manually.
I am wondering what the cause of this is, and how to deal with the issue in such a way that manual reconfiguration is not needed after every reboot.
xinput
asked Apr 20 at 16:43
Nonnus
254
add a comment |Â
up vote
1
down vote
favorite
On Linux, I use xinput set-prop to enable tapping the touchpad to click. To find the relevant device id as well as property number, I use xinput list-props.
Unfortunately, I find that both the device id and property number are not consistent across sessions. After a reboot, I often need to reconfigure these manually.
I am wondering what the cause of this is, and how to deal with the issue in such a way that manual reconfiguration is not needed after every reboot.
xinput
asked Apr 20 at 16:43
Nonnus
254
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
On Linux, I use xinput set-prop to enable tapping the touchpad to click. To find the relevant device id as well as property number, I use xinput list-props.
Unfortunately, I find that both the device id and property number are not consistent across sessions. After a reboot, I often need to reconfigure these manually.
I am wondering what the cause of this is, and how to deal with the issue in such a way that manual reconfiguration is not needed after every reboot.
xinput
asked Apr 20 at 16:43
Nonnus
254
On Linux, I use xinput set-prop to enable tapping the touchpad to click. To find the relevant device id as well as property number, I use xinput list-props.
Unfortunately, I find that both the device id and property number are not consistent across sessions. After a reboot, I often need to reconfigure these manually.
I am wondering what the cause of this is, and how to deal with the issue in such a way that manual reconfiguration is not needed after every reboot.
xinput
asked Apr 20 at 16:43
Nonnus
254
asked Apr 20 at 16:43
Nonnus
254
asked Apr 20 at 16:43
Nonnus
254
asked Apr 20 at 16:43
Nonnus
254
254
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The way to handle this is to write your own xorg.conf file (or put a file in the subdirectory where xorg.conf parts are collected, if your distribution does it that way), and use the InputClass section to match your device using vendor and device id or other hardware identifiers, and then apply the InputDevice options that are also valid for the InputClass section to enable tapping on the touchpad, or whatever else you want to configure.
Careful, the option names can be slightly different from the xinput names, so look closely. Inspect /var/log/Xorg.0.log after (re-)starting the X server to see if it worked.
See man xorg.conf for options, or google for tutorials (there should be quite a few).
answered Apr 21 at 8:45
dirkt
14k2930
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The way to handle this is to write your own xorg.conf file (or put a file in the subdirectory where xorg.conf parts are collected, if your distribution does it that way), and use the InputClass section to match your device using vendor and device id or other hardware identifiers, and then apply the InputDevice options that are also valid for the InputClass section to enable tapping on the touchpad, or whatever else you want to configure.
Careful, the option names can be slightly different from the xinput names, so look closely. Inspect /var/log/Xorg.0.log after (re-)starting the X server to see if it worked.
See man xorg.conf for options, or google for tutorials (there should be quite a few).
answered Apr 21 at 8:45
dirkt
14k2930
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
add a comment |Â
up vote
1
down vote
accepted
The way to handle this is to write your own xorg.conf file (or put a file in the subdirectory where xorg.conf parts are collected, if your distribution does it that way), and use the InputClass section to match your device using vendor and device id or other hardware identifiers, and then apply the InputDevice options that are also valid for the InputClass section to enable tapping on the touchpad, or whatever else you want to configure.
Careful, the option names can be slightly different from the xinput names, so look closely. Inspect /var/log/Xorg.0.log after (re-)starting the X server to see if it worked.
See man xorg.conf for options, or google for tutorials (there should be quite a few).
answered Apr 21 at 8:45
dirkt
14k2930
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The way to handle this is to write your own xorg.conf file (or put a file in the subdirectory where xorg.conf parts are collected, if your distribution does it that way), and use the InputClass section to match your device using vendor and device id or other hardware identifiers, and then apply the InputDevice options that are also valid for the InputClass section to enable tapping on the touchpad, or whatever else you want to configure.
Careful, the option names can be slightly different from the xinput names, so look closely. Inspect /var/log/Xorg.0.log after (re-)starting the X server to see if it worked.
See man xorg.conf for options, or google for tutorials (there should be quite a few).
answered Apr 21 at 8:45
dirkt
14k2930
The way to handle this is to write your own xorg.conf file (or put a file in the subdirectory where xorg.conf parts are collected, if your distribution does it that way), and use the InputClass section to match your device using vendor and device id or other hardware identifiers, and then apply the InputDevice options that are also valid for the InputClass section to enable tapping on the touchpad, or whatever else you want to configure.
Careful, the option names can be slightly different from the xinput names, so look closely. Inspect /var/log/Xorg.0.log after (re-)starting the X server to see if it worked.
See man xorg.conf for options, or google for tutorials (there should be quite a few).
answered Apr 21 at 8:45
dirkt
14k2930
answered Apr 21 at 8:45
dirkt
14k2930
answered Apr 21 at 8:45
dirkt
14k2930
answered Apr 21 at 8:45
dirkt
14k2930
14k2930
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
add a comment |Â
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
Thanks! The Arch Wiki was able to help me work out the details. wiki.archlinux.org/index.php/Touchpad_Synaptics
– Nonnus
Apr 26 at 21:42
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f438991%2finconsistent-device-and-property-labels-with-xinput%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
