Bug 348328 - cannot edit touchpad tap settings beyond enabling/disabling Mouse Click Emulation
Summary: cannot edit touchpad tap settings beyond enabling/disabling Mouse Click Emula...
Status: RESOLVED DUPLICATE of bug 344958
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:
Keywords:
: 348311 362370 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-05-27 19:31 UTC by Be
Modified: 2020-01-22 21:34 UTC (History)
6 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 Be 2015-05-27 19:31:29 UTC
The only option I can change regarding touchpad tapping is toggling Mouse Click Emulation. I can not edit any options modifying mouse click emulation though.

Reproducible: Always

Steps to Reproduce:
1. Open System Settings > Input Devices > Touchpad
2. Check "Mouse Click Emulation"
3. Try to change any other touchpad settings

Actual Results:  
Text for "One/Two/Three Finger(s)" options becomes active (not greyed out) but the drop down menus stay greyed out and I cannot change them. All other options on the tab remain greyed out.

Expected Results:  
I can edit all settings on the tab after enabling Mouse Click Emulation.

This is using Fedora 22 on a Lenovo Ideapad Z570 laptop.
Comment 1 Rajeesh K V 2015-05-27 19:47:16 UTC
Fedora 22 comes with new, simplified input driver called Libinput. This has streamlined and simplified many options previously exposed by synaptics driver. So, to have minimal impact, Touchpad KCM disables all options not configurable under Libinput driver and still works the same with old synaptics driver. See http://fedoraproject.org/wiki/Changes/LibinputForXorg

If you like to use the synaptics driver and all the configurable options, you can simply remove the xorg-x11-drv-libinput and install xorg-x11-drv-synaptics.

Closing this bug as touchpad kcm works as intended.
Comment 2 Be 2015-05-27 20:26:47 UTC
From my point of view as a user, libinput is oversimplified. Many of the configuration options in KCM Touchpad were useful features that I liked changing from the defaults. Most importantly, I use "Middle Click" much more often than "Right Click" so I like to set "Middle Click" to two finger taps and "Right Click" to three finger taps. Getting my touchpad to register three simultaneous finger taps accurately is more difficult than getting it to recognize two.

As a quick bandage solution, KCM Touchpad should explain why features are disabled and explain how to enable them. As it is now, it just looks broken. Better yet, libinput should support changing all these options.
Comment 3 Be 2015-05-27 22:09:15 UTC
I uninstalled xorg-x11-drv-libinput. xorg-x11-drv-synaptics was already installed. I restarted X and now KCM Touchpad says "No touchpad found" in a red box at the top and tap-to-click is not working.
Comment 4 Rajeesh K V 2015-06-01 07:59:25 UTC
*** Bug 348311 has been marked as a duplicate of this bug. ***
Comment 5 Marcos Leandro 2015-06-18 00:47:56 UTC
(In reply to Be from comment #3)
> I uninstalled xorg-x11-drv-libinput. xorg-x11-drv-synaptics was already
> installed. I restarted X and now KCM Touchpad says "No touchpad found" in a
> red box at the top and tap-to-click is not working.

Just reinstall xorg-x11-drv-synaptics package and it'll work.
Comment 6 Niels 2015-06-20 10:31:27 UTC
On Fedora 22:
I uninstalled xorg-x11-drv-libinput and reinstalled xorg-x11-drv-synaptics. The kcm now says "no touchpad found" and I can't change any settings. The touchpad apparently works fine.
Comment 7 Rajeesh K V 2015-06-20 18:35:20 UTC
The issue with 'no touchpad found' is tracked in bug#344958.
Can this bug be closed, as per comment#1?
Comment 8 Rex Dieter 2015-06-21 03:08:20 UTC
ok, let's do that.

*** This bug has been marked as a duplicate of bug 344958 ***
Comment 9 Rajeesh K V 2016-04-28 08:25:57 UTC
*** Bug 362370 has been marked as a duplicate of this bug. ***