Bug 411114 - Some touchpad settings get lost after waking up from sleep
Summary: Some touchpad settings get lost after waking up from sleep
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.25.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 458437 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-20 20:33 UTC by m.wege
Modified: 2024-03-25 02:34 UTC (History)
12 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 m.wege 2019-08-20 20:33:20 UTC
I have a surface Go running Kubuntu 19.04 with the fresh KDE packages. I have configured the Touchpad of the Surface Type cover to react to:
tap-to-click (Tippen zum Klicken), Berühren und Ziehen (don't know what it means in English) and Tap and drag lock.

It works, but when the device wakes up after sleep the settings are gone. In general the touchpad works, but not these settings.
Comment 1 Unlisted Person 2019-09-27 18:38:54 UTC
I have what may be a similar problem. 

See if 
(a) all the settings are reset and not just those you've modified 
(b) if the id for that device changed after sleep/wakeup.  

To find your touchpad id run: 

$ xinput list

and you should get something like

⎡ Virtual core pointer                          id=2    [master pointer  (3)]
...
⎜   ↳ SYNA307B:00 06CB:CD46 Touchpad            id=15   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=19   [slave  pointer  (2)]
...


Then to see what the settings are run 

$ xinput list-props 15
Device 'SYNA307B:00 06CB:CD46 Touchpad':
        Device Enabled (184):   1
        Coordinate Transformation Matrix (186): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Tapping Enabled (349): 0
        libinput Tapping Enabled Default (350): 0
        libinput Tapping Drag Enabled (351):    1
        libinput Tapping Drag Enabled Default (352):    1
        libinput Tapping Drag Lock Enabled (353):       0
        libinput Tapping Drag Lock Enabled Default (354):       0
        libinput Tapping Button Mapping Enabled (355):  1, 0
        libinput Tapping Button Mapping Default (356):  1, 0
        libinput Natural Scrolling Enabled (357):       0
        libinput Natural Scrolling Enabled Default (358):       0
        libinput Disable While Typing Enabled (359):    1
        libinput Disable While Typing Enabled Default (360):    1
        libinput Scroll Methods Available (361):        1, 1, 0
        libinput Scroll Method Enabled (362):   1, 0, 0
        libinput Scroll Method Enabled Default (363):   1, 0, 0
        libinput Click Methods Available (364): 1, 1
        libinput Click Method Enabled (365):    1, 0
        libinput Click Method Enabled Default (366):    1, 0
        libinput Middle Emulation Enabled (367):        0
        libinput Middle Emulation Enabled Default (368):        0
        libinput Accel Speed (369):     0.888476
        libinput Accel Speed Default (370):     0.000000
        libinput Left Handed Enabled (371):     0
        libinput Left Handed Enabled Default (372):     0
        libinput Send Events Modes Available (303):     1, 1
        libinput Send Events Mode Enabled (304):        0, 0
        libinput Send Events Mode Enabled Default (305):        0, 0
        Device Node (306):      "/dev/input/event22"
        Device Product ID (307):        1739, 52550
        libinput Drag Lock Buttons (373):       <no items>
        libinput Horizontal Scroll Enabled (374):       1

and you can see if they change before/after wake sleep. 

For me there's a workaround from a kernel bug where i2c_hid drivers cause interrupts for the Touchpad to go nuts on sleep/resume (modprobe -r/modprobe) but it causes xinput settings to be lost and the Device IDs 
to change on sleep/resume. If that's your case too then you can create a systemd script file to use on resume from sleep that executes something like 

"xinput 'device_name_here' 'libinput Tapping Enabled' 1" 

(or whatever your setting is) to restore the xinput settings you had before sleep.
Comment 2 hexclover 2020-01-19 11:08:01 UTC
I think have this problem, too.

Due to a kernel bug I have to reload the module in charge of my touchpad on resume from hibernation. Unfortunately this causes all settings configured through KCM to be reset to libinput defaults after resuming.

I have tried these two methods to restore my settings and they both work:

1. After resume, open Touchpad KCM, click some checkbox twice and apply the settings again.
2. Create an Xorg configuration file with the corresponding options.

So will it solve this issue if KDE just applies its touchpad settings again automatically on resume?
Comment 3 assaulth3ro911 2020-02-20 13:56:49 UTC
On Manjaro, KDE Plasma 5.17.5 I have this same issue. When it wakes from sleep, my Acer Switch Alpha (a 2-in-1 detachable) loses all touchpad settings, so it goes back to being slow and having the tap to click settings being lost.

Oh and the entire keyboard is lost, on top of that. I have to detach and reattach it post sleep to get it to work again.
Comment 4 Nate Graham 2020-03-19 14:14:25 UTC
Is anyone able to reproduce this with Plasma 5.18? I am not.
Comment 5 assaulth3ro911 2020-03-31 02:52:47 UTC
I can confirm this still happens on Plasma 5.18.3 with Manjaro. Also notable is the fact that upon waking my entire keyboard (which has the touchpad on it) doesn't come back either, I have to detach and reattach it to make it begin working again for me.

This is on an Acer Switch Alpha, about 2016 or so model.
Comment 6 kabud 2020-05-09 04:38:26 UTC
Can reproduce on kubuntu 20.04, plasma 4:5.18.4.1-0ubuntu1. (No problem with my keyboard)
Comment 7 Frank Steinmetzger 2020-06-09 20:30:08 UTC
I found this bug report because I observed something similar. My tap-to-touch seems to work after suspend. But I am having this reset problem after re-attaching the type cover. I looked at the output of xinput list-props per comment #1, and the only difference is Tapping Enabled and Accel Speed. Those are the two settings I changed in the touchpad KCM. The IDs listed by xinput list do not change after I dis- and then reconnected the type cover.

KDE Plasma 5.18.5, Frameworks 5.70.0, Arch packages.
Comment 8 Nate Graham 2020-06-09 23:14:36 UTC
I just had this happen recently after installing or removing some packages on openSUSE TUmbleweed but I can't remember that they were. :(
Comment 9 Dominik 2020-08-31 04:34:07 UTC
this is super annoying on my 2013 era macbook pro. when I wake from hibernate my touchpad settings are back to default. I have to manually uncheck, then check the "invert the scrolling" option and hit apply for it to engage. Tap to click is also constantly enabled which I hate but turning it off doesn't stick.  I accidentally got bumped from LTS kernel 5.4.58 to 5.7 and thought that had caused it but going back to 5.4 did not help. I don't remember this happening a month ago but don't know what I could have installed to cause this....
Comment 10 Nate Graham 2022-04-11 13:42:13 UTC
We have a report of this happening for mouse settings too: Bug 435113
Comment 11 f.schmitt 2022-08-28 17:37:27 UTC
I have the same Problem with earlier kubuntu distributions and now with kubuntu 22.10 (plasma 5.25.4)  and a surface pro 3. Issue appears when waking up from sleep and de- / attaching the keyboard.
Comment 12 Nate Graham 2022-08-30 21:57:48 UTC
*** Bug 458437 has been marked as a duplicate of this bug. ***
Comment 13 Nate Graham 2024-03-25 02:34:08 UTC
This was fixed a while ago. Sorry for missing it until now.