Bug 374214 - "Disable touchpad when typing" option does nothing with xf86-input-libinput
Summary: "Disable touchpad when typing" option does nothing with xf86-input-libinput
Status: RESOLVED DUPLICATE of bug 387153
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-27 16:11 UTC by Nicolas F.
Modified: 2020-01-22 21:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas F. 2016-12-27 16:11:33 UTC
With xf86-input-libinput, turning off the "Disable touchpad when typing" option in the "Enable/Disable Touchpad" tab seemingly has no effect, as demonstrated by xinput list-props not changing.

It appears that libinput integration in general is quite poor, as quite a few options are greyed out. Furthermore, the version of systemsettings which I'm using (5.8.4) is not even listed as an option in the bugtracker. Is this software unmaintained?
Comment 1 Adam Pigg 2017-07-16 09:37:34 UTC
Same here on openSuse Tumbleweed, using plasma 5.10.3.

I would like to enable 'disable touchpad while typing' but the setting makes no difference.  Taps are still detected which can be frustrating.
Comment 2 Nate Graham 2017-08-10 20:12:27 UTC
As you have discovered, Libinput support here is poor to nonexistent. Fixing that is tracked with https://bugs.kde.org/show_bug.cgi?id=383379

As a workarounfd, you can either remove Libinput or configure it via .conf files if you're using Xorg: https://wiki.archlinux.org/index.php/Libinput#Configuration

*** This bug has been marked as a duplicate of bug 383379 ***
Comment 3 Nate Graham 2017-11-20 16:09:46 UTC
Libinput support is currently only active in Wayland. This setting works fine in the Wayland version, but we can't access it from X11 yet. Duping this to

*** This bug has been marked as a duplicate of bug 387153 ***