Bug 447099

Summary:	Plasma Mobile Sleep timer does not listen for gamepads
Product:	[Plasma] kwin	Reporter:	William Ethridge <gamerminstrel>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	nate, nicolas.fella, xaver.hugl
Priority:	NOR	Keywords:	wayland
Version:	unspecified
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description William Ethridge 2021-12-16 23:33:03 UTC

SUMMARY

I am using a Pinephone, running Manjaro+Plasma Mobile. If I stop using the touch screen and instead start using a gamepad (such as the Razer Kishi), whatever function turns the device to sleep for inactivity does not listen for it. The screen will dim after a few seconds, and the screen will lock within a minute

STEPS TO REPRODUCE
1. open up a game like Retroarch
2. Try using gamepad instead of the touch screen
3. Pinephone will fall asleep after 1 minute.

OBSERVED RESULT
Phone goes to sleep 

EXPECTED RESULT
Device should stay awake so long as it detects gamepad inputs

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro-ARM/KDE Plasma
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

Comment 1 Nate Graham 2021-12-17 19:27:45 UTC

Plasma Mobile issues are tracked at https://invent.kde.org/groups/plasma-mobile/-/issues; can you re-file this over there? Thanks!

Comment 2 Nicolas Fella 2021-12-17 21:56:25 UTC

This is most likely not specific to Plasma Mobile so let's keep it here

Comment 3 William Ethridge 2021-12-18 16:26:38 UTC

Is it possible to tell KDE to not hibernate if specific applications are running? That might be an acceptable workaround for at least my use-case. After all, I think I would only be using a gamepad when I am playing a game.

Comment 4 Vlad Zahorodnii 2022-01-26 16:23:15 UTC

As far as I know, kwin doesn't handle gamepad input because libinput doesn't support it. And it's still up in the air whether the compositor should do that.

Comment 5 Zamundaaa 2024-06-06 17:02:58 UTC


*** This bug has been marked as a duplicate of bug 328987 ***