Bug 489362 - After resuming from suspend (close/open lid) sometimes the touchpad requires two fingers to work
Summary: After resuming from suspend (close/open lid) sometimes the touchpad requires ...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: input (show other bugs)
Version: 6.1.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-28 09:48 UTC by Massimiliano L
Modified: 2024-07-01 11:34 UTC (History)
1 user (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 Massimiliano L 2024-06-28 09:48:33 UTC
SUMMARY
When resuming work on my laptop after sleep / closing the lid, sometimes the touchpad is unrensponsive and requires two fingers to move the pointer.


STEPS TO REPRODUCE
1. Work with your laptop normally
2. Close the lid 
3. Open the lid
4. Go through 1-2-3 a few times until the problem appears.

OBSERVED RESULT
The touchpad does not respond to the usual one-finger operation, while using two fingers can move the cursor.

EXPECTED RESULT
The touchpad works normally.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 7490

ADDITIONAL INFORMATION
I observed this behaviour on the GNOME Session as well, but I never experienced on Plasma X11. This could point to an upstream issue (Wayland).

Switching to a virtual terminal and then back to the desktop fixes the issue. Similar issues have been reported in the past 2+ years across several platforms: https://askubuntu.com/questions/1387034/touchpad-starts-requiring-2-fingers-way-to-fix
Comment 1 Zamundaaa 2024-06-28 11:23:45 UTC
Please report this at https://gitlab.freedesktop.org/libinput/libinput/-/issues
Comment 2 Massimiliano L 2024-07-01 11:34:29 UTC
(In reply to Zamundaaa from comment #1)
> Please report this at
> https://gitlab.freedesktop.org/libinput/libinput/-/issues

Thank you for the pointer.

It seems it is indeed a known libinput issue, but apparently hard to debug for devs: https://gitlab.freedesktop.org/libinput/libinput/-/issues/712