https://bugs.kde.org/show_bug.cgi?id=486292
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
CC| |jpe...@petsovits.com
Status|REPORTED |RESOLVED
--- Comment #1 from Jakob Petsovits <jpe...@petsovits.com> ---
Duplicate of a long-running bug, I don't think this is even a regression, I
think Plasma never handled this properly. Steam/Wine should ideally set an idle
inhibitor. As a user one can do this by wrapping a command (either the game or
Steam itself) with systemd-inhibit. You can also manually block suspend using
the power management applet.
A proper solution unfortunately isn't as easy as inhibiting all fullscreen
apps, because regular apps or websites can also go fullscreen and it wouldn't
be right to auto-inhibit those without a clearer indication that those are
games or media which need this. The root cause is that libinput doesn't handle
game controllers like it handles touchpads, mice, keyboards and other input
devices, so KWin does not register the controller as user activity and will
eventually send an inactivity signal to PowerDevil.
I tried my hand on a daemon to monitor controller inputs, unfortunately this
has side effects as the kernel will automatically disable mouse emulation once
any process opens the controller input device explicitly. So that would be
simply switching one annoying bug for another. According to the KWin guys, the
proper solution would be to have KWin itself open the game controller input
device, do its own mouse emulation if no other process uses the controller, and
have controller input activity reset the inactivity timer.
*** This bug has been marked as a duplicate of bug 328987 ***
--
You are receiving this mail because:
You are watching all bug changes.
