Public bug reported:
As the title says, when using the hidraw as input method, used by game
controllers in games in Steam big picture mode especially, is not being
detected by the gnome desktop, and so if you are playing a game using
hidraw only, the screen timeout will come out, and the session will be
blocked
Steps to reproduce:
- Open a game
- Play a game with a controller using hidraw as input, such as the RPCS3
emulator
- The gnome-screensaver timeout will kick in and lock the session even when
actively playing, as long no mouse or keyboard is used
What should happen
- Hidraw should be detected in the same way a mouse or keyboard does
I have NOT tested with a game using native evdev
My config is:
Steam + steam-devices packages installed, the steam devices has some rules for
hidraw to be correctly working with my controller.
I own a PS4 controller connected via bluetooth, but the same should happen on
USB as well
I used the RPCS3 emulator, which so far supports only hidraw as input method.
** Affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
As the title says, when using the hidraw as input method, used by game
- controllers in games like Steam especially, is not being detected by the
- gnome desktop, and so if you are playing a game using hidraw with the
- controller, the screen timeout will come out, and the session will be
+ controllers in games in Steam big picture mode especially, is not being
+ detected by the gnome desktop, and so if you are playing a game using
+ hidraw only, the screen timeout will come out, and the session will be
blocked
Steps to reproduce:
- Open a game
- Play a game with a controller using hidraw as input, such as the RPCS3
emulator
- The gnome-screenshot timeout will kick in and lock the session even when
actively playing, as long no mouse or keyboard is used
What should happen
- Hidraw should be detected in the same way a mouse or keyboard does
I have NOT tested with a game using native evdev
My config is:
Steam + steam-devices packages installed, the steam devices has some rules
for hidraw to be correctly working with my controller.
I own a PS4 controller connected via bluetooth, but the same should happen on
USB as well
I used the RPCS3 emulator, which so far supports only hidraw as input method.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1834762
Title:
Screen locks after timeout with hidraw input
Status in gnome-screensaver package in Ubuntu:
New
Bug description:
As the title says, when using the hidraw as input method, used by game
controllers in games in Steam big picture mode especially, is not
being detected by the gnome desktop, and so if you are playing a game
using hidraw only, the screen timeout will come out, and the session
will be blocked
Steps to reproduce:
- Open a game
- Play a game with a controller using hidraw as input, such as the RPCS3
emulator
- The gnome-screensaver timeout will kick in and lock the session even when
actively playing, as long no mouse or keyboard is used
What should happen
- Hidraw should be detected in the same way a mouse or keyboard does
I have NOT tested with a game using native evdev
My config is:
Steam + steam-devices packages installed, the steam devices has some rules
for hidraw to be correctly working with my controller.
I own a PS4 controller connected via bluetooth, but the same should happen on
USB as well
I used the RPCS3 emulator, which so far supports only hidraw as input method.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
