| 2019-06-30 01:22:03 |
Luca Osvaldo Mastromatteo |
bug |
|
|
added bug |
| 2019-06-30 01:23:37 |
Luca Osvaldo Mastromatteo |
description |
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 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. |
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-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. |
|
| 2019-06-30 01:29:41 |
Luca Osvaldo Mastromatteo |
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-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. |
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. |
|
| 2019-06-30 01:31:04 |
Luca Osvaldo Mastromatteo |
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. |
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 package has some udev rules for hidraw to be correctly working with this 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. |
|
| 2019-06-30 01:32:39 |
Luca Osvaldo Mastromatteo |
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 package has some udev rules for hidraw to be correctly working with this 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. |
As the title says, when using 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 blank screen and/or lock timeout will come out, and the session will be blocked or the screen will become blank
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 package has some udev rules for hidraw to be correctly working with this 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. |
|
