-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F key toggles fullscreen mode #1637
Comments
Someone reported this for Stalker 2 but it worked on my machine when I tried to get it to happen. does it happen in any other particular games? |
I also had this problem in Stalker 2, but now I can't reproduce it. This also was happening in Deus Ex: Revision. I guess it only happens under some condition which is yet to be found. |
Someone encountered same problem on reddit: https://www.reddit.com/r/linux_gaming/comments/1gxn5fr/wine_wayland_woes/ |
This seems to be related to the numpad. When I turn off the numpad, the F key won't toggle fullscreen anymore. |
Turning off num-lock also solved the issue for me as well. While running gamescope and num-lock enabled, the "F" key would toggle fullscreen. I also had other keys that would be unusable such as "S" and "O". If not using gamescope and num-lock was enabled. All keys worked normally. |
Is everyone experiencing this using Plasma, or has it happened to anyone on other DEs as well? |
I'm on Plasma 6.2.3. |
I'm on Plasma 6.2.3 on Arch and have run into the issue as well. Initially I was trying to look for some trigger for it happening, like launching gamescope from the Steam launch options or some other program interfering, but I had it happen immediately after a reboot without Steam autostarting, simply with Unless I hear otherwise, it makes me wonder if we're hitting a bug somewhere else in Plasma that's being expressed by gamescope's hotkey usage tbh. Probably won't have time to look into it myself for a few days but I do think getting some input logs out of KDE would be good to see if they line up with what I see in Gamescope when I add logging for when various "Meta + [x]" functions get called within gamescope. EDIT: interesting... libinput debug-events look identical for when it's working correctly and not correctly |
Same issue here in several games. This seems to be indeed a gamescope bug; it appears in several games i have tested and immediately vanishes when launching the same games without gamescope. Disabling numpad works too for me as a temporary workaround but this is not convenient, hope this gets a fix. Let me know if i can help providing logs or testing stuff. |
@jbellionjourdan which desktop environment/session type?
|
Wayland, KDE Plasma 6. On Garuda linux (arch). |
I spent around 20 minutes trying to reproduce the issue on Gnome (Wayland) but I was unable to, so I'm leaning towards this being some bug between KDE and gamescope. I will look for any related reports about hotkey issues on KDE's bug tracker and file a new issue if I don't find any. |
Yeah might be. On my side it's pretty straightforward to reproduce, if numlock is on then gamescope shortcuts behave as if meta were always pressed. Don't need to restart the game either, just pressing the numlock key instantly toggles the issue on and off. |
I see the issue with |
For now I've reported the issue here: https://bugs.kde.org/show_bug.cgi?id=497050 I want to keep testing Gnome for a bit just to double-check that the issue really never happens there. |
yes KDE here same problem.. shorcuts not work on latest gamescope |
…kend Per Wayland protocol specsheet regarding keymapping: "From version 7 onwards, the fd must be mapped with MAP_PRIVATE by the recipient, as MAP_SHARED may fail." This matches up exactly with what we're seeing with this error: [gamescope] [Error] xdg_backend: Failed to map keymap fd. Changing MAP_SHARED to MAP_PRIVATE per the spec addresses this error. Fixes: ValveSoftware#1658 (hopefully) fixes: ValveSoftware#1637
Per Wayland protocol specsheet regarding keymapping: "From version 7 onwards, the fd must be mapped with MAP_PRIVATE by the recipient, as MAP_SHARED may fail." This matches up exactly with what we're seeing with this error: [gamescope] [Error] xdg_backend: Failed to map keymap fd. Changing MAP_SHARED to MAP_PRIVATE per the spec addresses this error. Fixes: ValveSoftware#1658 (hopefully) fixes: ValveSoftware#1637
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
When I press F games in with "exclusive fullscreen" mode gamescope toggles its fullscreen mode. Just F without any modifiers.
Steps To Reproduce
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
No response
The text was updated successfully, but these errors were encountered: