You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Wayland systems, the ESCAPE button must be pressed twice for the input to go to the game being played. The first escape unlocks the mouse and the second escape is input towards the game.
The expected response is for the mouse to not be unlocked and the input to go towards the game the first time.
To Reproduce
Open a game in Geforce NOW
Press the Escape button when using the Wayland display server
Mouse will unlock
Press the Escape button again
Menu should now pop up as expected
Screenshots
No response
Operating System
Fedora
Desktop Environment
GNOME 46.5
Display Server
Wayland
Installation method
AppImage
Version
2.1.2
Is this a fresh install of the app or an update from a past version?
Fresh install
Did this issue appear right away upon installation/updating, or spontaneously?
Yes, right after installation
Additional context
No response
The text was updated successfully, but these errors were encountered:
This issue may be a duplicate of #137 but I believe this is a different issue as most of the comments there state X11 as the display server while this issue only affects me on the Wayland display server instead.
Describe the bug
On Wayland systems, the ESCAPE button must be pressed twice for the input to go to the game being played. The first escape unlocks the mouse and the second escape is input towards the game.
The expected response is for the mouse to not be unlocked and the input to go towards the game the first time.
To Reproduce
Screenshots
No response
Operating System
Fedora
Desktop Environment
GNOME 46.5
Display Server
Wayland
Installation method
AppImage
Version
2.1.2
Is this a fresh install of the app or an update from a past version?
Fresh install
Did this issue appear right away upon installation/updating, or spontaneously?
Yes, right after installation
Additional context
No response
The text was updated successfully, but these errors were encountered: