Bug 406778 - KCM touchpad settings ignored in X11 session with Linux 5.0
Summary: KCM touchpad settings ignored in X11 session with Linux 5.0
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://bugzilla.kernel.org/show_bug....
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-22 16:04 UTC by Nicola Mori
Modified: 2020-01-22 21:34 UTC (History)
2 users (show)

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


Attachments
Touchpd configuration file for xorg. (164 bytes, text/plain)
2019-04-22 16:04 UTC, Nicola Mori
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicola Mori 2019-04-22 16:04:18 UTC
Created attachment 119564 [details]
Touchpd configuration file for xorg.

SUMMARY
Since I upgraded my system to Linux 5.0 the touchpad settings from KCM are ignored. Specifically, the tap-to-click can be set but is ignored, i.e. tap-to-click does not work. This happens without any xorg configuration files. If I add a configuration file /etc/X11/xorg.conf.d/30-touchpad.conf as the attached one then tap-to-click works again, but this time it cannot be disabled from the KCM module.

Everything works as expected with Linux 4.19.


STEPS TO REPRODUCE
1. Install Linux 5.0
2. Remove any xorg configuration file for the touchpad
3. Start Plasma

OBSERVED RESULT
The touchpad tap-to-click does not work, event when enabled from KCM.

EXPECTED RESULT
The touchpad tap-to-click behavior should comply with the KCM settings.

SOFTWARE/OS VERSIONS
System: Dell XPS 15 9570
$ dmesg |grep Touch
1216:[    3.814366] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x0, board id: 3125, fw id: 2378871
1217:[    3.850630] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input9
1234:[    4.833956] input: SYNA2393:00 06CB:7A13 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-10/i2c-SYNA2393:00/0018:06CB:7A13.0001/input/input15
1250:[    5.008216] input: SYNA2393:00 06CB:7A13 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-10/i2c-SYNA2393:00/0018:06CB:7A13.0001/input/input24


Linux/KDE Plasma: Archlinux with:
  linux-ck 5.0.9-1
  libinput 1.13.1-1
  xf86-input-libinput 0.28.2-1
  xorg-server 1.20.4-1

KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57
Qt Version: 5.12.2-2

ADDITIONAL INFORMATION
Comment 1 atulbi 2019-04-22 19:46:33 UTC
Have you tried libinput driver?
Comment 2 Nicola Mori 2019-04-23 09:12:21 UTC
@atulbi Actually I think that on my system there's just the libinput driver (e.g. no synaptic, I checked with the package manager); you can see the versions in my first message. Moreover, I load it explicitly when I use the attached xorg configuration file, but this does not make the KCM settings being respected.
Comment 3 Nate Graham 2019-04-23 15:36:33 UTC
If you're using Libinput rather than Synaptics, then this is unfortunately expected until https://bugs.kde.org/show_bug.cgi?id=387153 is implemented. Thankfully, it's in progress!

*** This bug has been marked as a duplicate of bug 387153 ***
Comment 4 Nicola Mori 2019-04-23 16:29:16 UTC
Thanks Nate, I knew about that bug report but I opened a new one since I think my experience is slightly different. With Linux 4.19 and without any xorg config file the KCM touchpad settings are honored. I thought that maybe in this configuration a different touchpad driver is used, even if I dont have synaptics installed and I am not aware of any other driver apart from libinput, but here's the content of Xorg.0.log:

[     6.854] (II) config/udev: Adding input device SYNA2393:00 06CB:7A13 Touchpad (/dev/input/event13)
[     6.854] (**) SYNA2393:00 06CB:7A13 Touchpad: Applying InputClass "libinput touchpad catchall"
[     6.854] (II) Using input driver 'libinput' for 'SYNA2393:00 06CB:7A13 Touchpad

So I guess that libinput is actually used, and KCM works fine in an X11 session with Linux 4.19. This does not fit with what bug report 387153 says; problems started only with Linux 5.0.
Comment 5 Nate Graham 2019-04-23 17:41:37 UTC
Ah, I see now, thanks. If the only thing that changed to cause this issue was you upgrading from 4.19 to 5.0, I think it makes sense to report this issue to the kernel folks. Once you do, please add the URL of the bug report to the "URL" field in this bug report. Thanks!
Comment 6 Nate Graham 2019-04-23 19:06:22 UTC
Thank you Nicola!