Bug 460852 - Touchscreen sometimes does not work after waking from suspend
Summary: Touchscreen sometimes does not work after waking from suspend
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: libinput (other bugs)
Version First Reported In: 5.26.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-22 15:14 UTC by Devin Lin
Modified: 2024-04-02 11:46 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Devin Lin 2022-10-22 15:14:38 UTC
SUMMARY
An issue we have been having in Plasma Mobile for as long as I can remember, is that the touchscreen sometimes stops being able to interact with anything after waking from suspend.

We have confirmed that libinput indeed is still receiving these touch events in these cases, however it seems something in between doesn't pass the events along.

We have an issue with more details here: https://invent.kde.org/teams/plasma-mobile/issues/-/issues/102

STEPS TO REPRODUCE
This only happens ~10% of the time, and I haven't found a reliable way to reproduce it, so it is hard to trace down: 
1. Suspend the phone
2. Wake the phone
3. Attempt to interact with the touchscreen
4. Attach keyboard and mouse, and unlock 
5. Attempt to interact with the touchscreen while logged in

OBSERVED RESULT
Apps and the shell don't seem to receiving any input events

EXPECTED RESULT
Apps and shell receive input events

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Plasma Mobile on postmarketOS and Manjaro
KDE Plasma Version: 5.26
KDE Frameworks Version: 5.98
Qt Version: 5.15.6
Comment 1 Devin Lin 2022-10-22 15:40:45 UTC
I've also noticed that if the screen dims due to inactivity, touching the screen seems to work to make it undim. So something is wrong in actually passing the events to the UI.
Comment 2 Zamundaaa 2024-04-02 11:46:52 UTC
I just found this bug report in a search; afaict from the linked issue it can be closed