Please describe your issue in as much detail as possible:
After launching a game on a Plasma X11 session using gamescope -f --force-grab-cursor -- %command% in the Steam Deck client, touch input stops working within the Steam client after the game is closed. I tested this on both Steam Deck OLED and ROG Ally, on SteamOS and upstream Arch, and both present this issue in the same way. Plasma Wayland seems unaffected.
Steps for reproducing this issue:
Launch a game (I used Grim Dawn and Hades II) with gamescope -f --force-grab-cursor -- %command% while on SteamOS Stable
Use the touchpad as a mouse for a few seconds once in-game, and tap the screen a couple times for good measure
Close the application
Attempt to use touch input within the Steam client after the game is fully closed
The cursor should disappear at this point, and start presenting weird behavior like dragging stuff as if you were holding down the touchpad. The behavior goes back to normal after restarting the Steam client.
I think this is a Steam client issue, although it's hard to say for sure given the additional factor of gamescope in the equation.
Your system information
Please describe your issue in as much detail as possible:
After launching a game on a Plasma X11 session using
gamescope -f --force-grab-cursor -- %command%in the Steam Deck client, touch input stops working within the Steam client after the game is closed. I tested this on both Steam Deck OLED and ROG Ally, on SteamOS and upstream Arch, and both present this issue in the same way. Plasma Wayland seems unaffected.Steps for reproducing this issue:
gamescope -f --force-grab-cursor -- %command%while on SteamOS StableThe cursor should disappear at this point, and start presenting weird behavior like dragging stuff as if you were holding down the touchpad. The behavior goes back to normal after restarting the Steam client.
I think this is a Steam client issue, although it's hard to say for sure given the additional factor of gamescope in the equation.