Bug 391693 - Touchpad settings are lost after resume if there is a mismatch between Touchpad-KCM and xorg.conf
Summary: Touchpad settings are lost after resume if there is a mismatch between Touchp...
Status: RESOLVED DUPLICATE of bug 387153
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-11 00:54 UTC by jeremy9856
Modified: 2020-01-22 21:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jeremy9856 2018-03-11 00:54:34 UTC
Hello,

The touchpad settings are often lost after resume. Note that I have a chromebook and I need to disable the touchpad on suspend (rmmod cyapatp) and reenable it on resume (modprobe cyapatp).

Thanks !
Comment 1 jeremy9856 2018-03-15 22:03:01 UTC
I think I workaround it by putting the settings in a file in xorg.conf.d

Section "InputClass"
    Identifier "libinput touchpad catchall"
    MatchIsTouchpad "on"
    Driver "libinput"
    Option "TappingDrag" "false"
    Option "Tapping" "true"
EndSection
Comment 2 jeremy9856 2018-03-16 12:05:50 UTC
Note that I was already using the same settings file in xorg.conf.d to disable TappingDrag that doesn't have a setting in GUI but without "Option "Tapping" "true"" that I had set with the GUI. After I added "Option "Tapping" "true"" to the file the touchpad settings won't be lost anymore.
Comment 3 Nate Graham 2018-03-29 14:23:35 UTC
(In reply to jeremy9856 from comment #0)
> Note that I have a
> chromebook and I need to disable the touchpad on suspend (rmmod cyapatp) and
> reenable it on resume (modprobe cyapatp).

This seems like a bug that should be fixed, not worked around. Please report it upstream to the libinput folks: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland (choose the "libinput" component).

Once the Touchpad KCM is re-done to actually support libinput, you'll be able to set those settings via the GUI rather than an xorg.conf file, and the issue described here will no longer be applicable.

*** This bug has been marked as a duplicate of bug 387153 ***
Comment 4 jeremy9856 2018-03-29 14:44:16 UTC
(In reply to Nate Graham from comment #3)
> (In reply to jeremy9856 from comment #0)
> > Note that I have a
> > chromebook and I need to disable the touchpad on suspend (rmmod cyapatp) and
> > reenable it on resume (modprobe cyapatp).
> 
> This seems like a bug that should be fixed, not worked around. Please report
> it upstream to the libinput folks:
> https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland (choose the
> "libinput" component).

That has nothing to do with libinput I think. I need to do this to avoid the touchpad to be active in suspend. Maybe I should report this to the cyapatp kernel driver ? I don't know. I just specified it in case that could interfere.

> Once the Touchpad KCM is re-done to actually support libinput, you'll be
> able to set those settings via the GUI rather than an xorg.conf file, and
> the issue described here will no longer be applicable.

That's right but I think the behavior is not right. IMHO the right behavior would be that the kde touchpad settings and the xorg touchpad settings (if used) should merge with kde touchpad settings having a higher priority. That's the real bug and FWIW it work perfectly on Gnome.