Bug 496943 - Touchpad becomes sluggish/choppy on restart and sleep
Summary: Touchpad becomes sluggish/choppy on restart and sleep
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: input (other bugs)
Version First Reported In: 6.2.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-02 17:37 UTC by minelorderagon16
Modified: 2025-01-03 03:47 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description minelorderagon16 2024-12-02 17:37:03 UTC 
SUMMARY
Upon restarting or waking from sleep, the touchpad sometimes (~50% of the time) stops functioning properly. the touchpad becomes unresponsive and laggy, registering clicks, zooming (when it can control it), and scrolling sporadically. Likely not a distro issue on account of reports from other distros that i have seen, primarily fedora and arch. touchpad typically continues functioning normally after sleeping and waking again, and often (though not always) does the same after restarting again.

STEPS TO REPRODUCE
1. restart system or enter sleep mode
2. log back in
3. observe touchpad behavior
4. if touchpad behaving as described, restart or sleep again
5. verify return to normal behavior

OBSERVED RESULT

EXPECTED RESULT
on some attempts the touchpad will become unresponsive and trigger inputs seemingly at random.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Tuxedo OS 4
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION
On a 2019 model (bought in 2020) lenovo legion 5 laptop. specs:
CPU: AMD ryzen 5 4600H w/ radepn iGPU
dGPU: gtx 1650
RAM: 16 GB
laptop model (doubt it's relevant but just in case): Lenovo Legion 5 15ARH05
Comment 1 David Edmundson 2024-12-03 16:52:27 UTC 
Can you run "evtest" before and after suspend.

it will list all raw events that happen on a given device before they get to kwin. You'll need to find that device and run the program as root.

It'll help to prove narrow down which layer the issue is at.
Comment 2 minelorderagon16 2024-12-04 16:51:36 UTC 
(In reply to David Edmundson from comment #1)
> Can you run "evtest" before and after suspend.
> 
> it will list all raw events that happen on a given device before they get to
> kwin. You'll need to find that device and run the program as root.
> 
> It'll help to prove narrow down which layer the issue is at

not sure how i'm supposed to submit it but

before suspend:
Event: time 1733330853.029820, -------------- SYN_REPORT ------------
Event: time 1733330853.037056, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 713
Event: time 1733330853.037056, type 3 (EV_ABS), code 0 (ABS_X), value 713
Event: time 1733330853.037056, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 741200
Event: time 1733330853.037056, -------------- SYN_REPORT ------------
Event: time 1733330853.044270, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 552
Event: time 1733330853.044270, type 3 (EV_ABS), code 1 (ABS_Y), value 552
Event: time 1733330853.044270, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 748500
Event: time 1733330853.044270, -------------- SYN_REPORT ------------
Event: time 1733330853.050756, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 553
Event: time 1733330853.050756, type 3 (EV_ABS), code 1 (ABS_Y), value 553
Event: time 1733330853.050756, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 755800
Event: time 1733330853.050756, -------------- SYN_REPORT ------------
Event: time 1733330853.057969, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 554
Event: time 1733330853.057969, type 3 (EV_ABS), code 1 (ABS_Y), value 554
Event: time 1733330853.057969, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 763000
Event: time 1733330853.057969, -------------- SYN_REPORT ------------
Event: time 1733330853.065241, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 555
Event: time 1733330853.065241, type 3 (EV_ABS), code 1 (ABS_Y), value 555
Event: time 1733330853.065241, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 770300
Event: time 1733330853.065241, -------------- SYN_REPORT ------------
Event: time 1733330853.072454, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 777600
Event: time 1733330853.072454, -------------- SYN_REPORT ------------
Event: time 1733330853.079622, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1733330853.079622, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1733330853.079622, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1733330853.079622, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 784800
Event: time 1733330853.079622, -------------- SYN_REPORT ------------

after suspend:
Event: time 1733331008.541746, -------------- SYN_REPORT ------------
Event: time 1733331008.549959, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 979
Event: time 1733331008.549959, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 177
Event: time 1733331008.549959, type 3 (EV_ABS), code 0 (ABS_X), value 979
Event: time 1733331008.549959, type 3 (EV_ABS), code 1 (ABS_Y), value 177
Event: time 1733331008.549959, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 3345900
Event: time 1733331008.549959, -------------- SYN_REPORT ------------
Event: time 1733331008.557166, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 987
Event: time 1733331008.557166, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 170
Event: time 1733331008.557166, type 3 (EV_ABS), code 0 (ABS_X), value 987
Event: time 1733331008.557166, type 3 (EV_ABS), code 1 (ABS_Y), value 170
Event: time 1733331008.557166, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 3353200
Event: time 1733331008.557166, -------------- SYN_REPORT ------------
Event: time 1733331008.564398, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 993
Event: time 1733331008.564398, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 164
Event: time 1733331008.564398, type 3 (EV_ABS), code 0 (ABS_X), value 993
Event: time 1733331008.564398, type 3 (EV_ABS), code 1 (ABS_Y), value 164
Event: time 1733331008.564398, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 3360400
Event: time 1733331008.564398, -------------- SYN_REPORT ------------
Event: time 1733331008.571604, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 998
Event: time 1733331008.571604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 159
Event: time 1733331008.571604, type 3 (EV_ABS), code 0 (ABS_X), value 998
Event: time 1733331008.571604, type 3 (EV_ABS), code 1 (ABS_Y), value 159
Event: time 1733331008.571604, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 3367600
Event: time 1733331008.571604, -------------- SYN_REPORT ------------
Event: time 1733331008.578755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1733331008.578755, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1733331008.578755, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1733331008.578755, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 3374800
Event: time 1733331008.578755, -------------- SYN_REPORT ------------

i stopped on the second immediately after the issue occurred to ensure it was there. i gave a small section of the output i got, but i can do it again with a larger section if needed.
Comment 3 Bug Janitor Service 2024-12-19 03:46:53 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-01-03 03:47:38 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.