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 !
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
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.
(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 ***
(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.