Configuring touchpad resolution with libinput

Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I got a ThinkPad x240 and it has some known issues with jumpy touchpad behaviour in linux because of the difference in horinzontal and vertical resolution.
The former solution (in xorg) was to put some config into /etc/X11/xorg.conf.d/ (see Here, Here). But now I am in Ubuntu 17.10 and therefor gnome with wayland.
xinput list shows the following:
â¡ Virtual core pointer id=2 [master pointer (3)]
â â³ Virtual core XTEST pointer id=4 [slave pointer (2)]
â â³ xwayland-pointer:13 id=6 [slave pointer (2)]
â â³ xwayland-relative-pointer:13 id=7 [slave pointer (2)]
⣠Virtual core keyboard id=3 [master keyboard (2)]
â³ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
â³ xwayland-keyboard:13 id=8 [slave keyboard (3)]
There are several files in /usr/share/X11/xorg.conf.d/: 10-amdgpu.conf 10-radeon.conf 50-synaptics.conf 10-quirks.conf 40-libinput.conf 70-wacom.conf
I tried adding the 50-synaptics.conf to match the one here except I changed the line MatchProduct to this MatchIsTouchpad "on".
I also tried editing the 40-libinput.conf:
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "VertResolution" "100"
Option "HorizResolution" "65"
Driver "libinput"
EndSection
None of this config files helped me solve my problem. Afaik the only 2 settings I need are VertResolution and HorizResolution. How can I set these for my touchpad and permanent?
xorg 17.10 touchpad synaptics libinput
add a comment |Â
up vote
0
down vote
favorite
I got a ThinkPad x240 and it has some known issues with jumpy touchpad behaviour in linux because of the difference in horinzontal and vertical resolution.
The former solution (in xorg) was to put some config into /etc/X11/xorg.conf.d/ (see Here, Here). But now I am in Ubuntu 17.10 and therefor gnome with wayland.
xinput list shows the following:
â¡ Virtual core pointer id=2 [master pointer (3)]
â â³ Virtual core XTEST pointer id=4 [slave pointer (2)]
â â³ xwayland-pointer:13 id=6 [slave pointer (2)]
â â³ xwayland-relative-pointer:13 id=7 [slave pointer (2)]
⣠Virtual core keyboard id=3 [master keyboard (2)]
â³ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
â³ xwayland-keyboard:13 id=8 [slave keyboard (3)]
There are several files in /usr/share/X11/xorg.conf.d/: 10-amdgpu.conf 10-radeon.conf 50-synaptics.conf 10-quirks.conf 40-libinput.conf 70-wacom.conf
I tried adding the 50-synaptics.conf to match the one here except I changed the line MatchProduct to this MatchIsTouchpad "on".
I also tried editing the 40-libinput.conf:
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "VertResolution" "100"
Option "HorizResolution" "65"
Driver "libinput"
EndSection
None of this config files helped me solve my problem. Afaik the only 2 settings I need are VertResolution and HorizResolution. How can I set these for my touchpad and permanent?
xorg 17.10 touchpad synaptics libinput
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I got a ThinkPad x240 and it has some known issues with jumpy touchpad behaviour in linux because of the difference in horinzontal and vertical resolution.
The former solution (in xorg) was to put some config into /etc/X11/xorg.conf.d/ (see Here, Here). But now I am in Ubuntu 17.10 and therefor gnome with wayland.
xinput list shows the following:
â¡ Virtual core pointer id=2 [master pointer (3)]
â â³ Virtual core XTEST pointer id=4 [slave pointer (2)]
â â³ xwayland-pointer:13 id=6 [slave pointer (2)]
â â³ xwayland-relative-pointer:13 id=7 [slave pointer (2)]
⣠Virtual core keyboard id=3 [master keyboard (2)]
â³ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
â³ xwayland-keyboard:13 id=8 [slave keyboard (3)]
There are several files in /usr/share/X11/xorg.conf.d/: 10-amdgpu.conf 10-radeon.conf 50-synaptics.conf 10-quirks.conf 40-libinput.conf 70-wacom.conf
I tried adding the 50-synaptics.conf to match the one here except I changed the line MatchProduct to this MatchIsTouchpad "on".
I also tried editing the 40-libinput.conf:
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "VertResolution" "100"
Option "HorizResolution" "65"
Driver "libinput"
EndSection
None of this config files helped me solve my problem. Afaik the only 2 settings I need are VertResolution and HorizResolution. How can I set these for my touchpad and permanent?
xorg 17.10 touchpad synaptics libinput
I got a ThinkPad x240 and it has some known issues with jumpy touchpad behaviour in linux because of the difference in horinzontal and vertical resolution.
The former solution (in xorg) was to put some config into /etc/X11/xorg.conf.d/ (see Here, Here). But now I am in Ubuntu 17.10 and therefor gnome with wayland.
xinput list shows the following:
â¡ Virtual core pointer id=2 [master pointer (3)]
â â³ Virtual core XTEST pointer id=4 [slave pointer (2)]
â â³ xwayland-pointer:13 id=6 [slave pointer (2)]
â â³ xwayland-relative-pointer:13 id=7 [slave pointer (2)]
⣠Virtual core keyboard id=3 [master keyboard (2)]
â³ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
â³ xwayland-keyboard:13 id=8 [slave keyboard (3)]
There are several files in /usr/share/X11/xorg.conf.d/: 10-amdgpu.conf 10-radeon.conf 50-synaptics.conf 10-quirks.conf 40-libinput.conf 70-wacom.conf
I tried adding the 50-synaptics.conf to match the one here except I changed the line MatchProduct to this MatchIsTouchpad "on".
I also tried editing the 40-libinput.conf:
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "VertResolution" "100"
Option "HorizResolution" "65"
Driver "libinput"
EndSection
None of this config files helped me solve my problem. Afaik the only 2 settings I need are VertResolution and HorizResolution. How can I set these for my touchpad and permanent?
xorg 17.10 touchpad synaptics libinput
xorg 17.10 touchpad synaptics libinput
asked Mar 18 at 18:11
Ben
1013
1013
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45
add a comment |Â
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
With all the different X implementations, The most reliable method is to set input device options is by using xinput as shown In this answer. In your case the "option name" you want to look for will be something like "resolution" depending how your device names the options.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
With all the different X implementations, The most reliable method is to set input device options is by using xinput as shown In this answer. In your case the "option name" you want to look for will be something like "resolution" depending how your device names the options.
add a comment |Â
up vote
2
down vote
With all the different X implementations, The most reliable method is to set input device options is by using xinput as shown In this answer. In your case the "option name" you want to look for will be something like "resolution" depending how your device names the options.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
With all the different X implementations, The most reliable method is to set input device options is by using xinput as shown In this answer. In your case the "option name" you want to look for will be something like "resolution" depending how your device names the options.
With all the different X implementations, The most reliable method is to set input device options is by using xinput as shown In this answer. In your case the "option name" you want to look for will be something like "resolution" depending how your device names the options.
answered Mar 18 at 18:33
stumblebee
2,3083922
2,3083922
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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%2faskubuntu.com%2fquestions%2f1017076%2fconfiguring-touchpad-resolution-with-libinput%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
At the login prompt, you can switch from wayland back to xorg, and maybe some of your previous work can work again. Wayland is not going to be the primary DE in 18.04, and may go away after that. It's just not up to the task yet.
â heynnema
Mar 18 at 18:45