Skip to content
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

gamescope behaves like super button is pressed permanently #1691

Closed
3 of 6 tasks
juliusmaximus167 opened this issue Jan 3, 2025 · 5 comments
Closed
3 of 6 tasks

gamescope behaves like super button is pressed permanently #1691

juliusmaximus167 opened this issue Jan 3, 2025 · 5 comments

Comments

@juliusmaximus167
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

When starting a game in gamescope some keys won't register.

Upon further testing and after reinstalling my OS, I noticed shortcuts were performed when pressing the keys that don't function. For example pressing f toggles fullscreen instead of putting the letter f into the login form of a game.

The super button is not pressed. It was working pre update to version 3.16.1 of gamescope.

Steps To Reproduce

  1. Launch Warframe from Steam with the gamescope launch command 'gamescope -W 3440 -H 1440 --hdr-enabled -f --force-grab-cursor -- %command%'
  2. Try to enter E-Mail/username and password
  3. Some keys don't register and execute hotkeys:
    Super + F toggle fullscreen
    Super + N toggle nearest neighbour filtering
    Super + U toggle FSR upscaling
    Super + Y toggle NIS upscaling
    Super + I increase FSR sharpness by 1
    Super + O decrease FSR sharpness by 1
    Super + S take a screenshot
    Super + G toggle keyboard grab

Hardware information

- Distro: EndeavourOS
- CPU: 8-core AMD Ryzen 7 7800X3D
- GPU: Advanced Micro Devices, Inc. [AMD/ATI] Navi 32 [Radeon RX 7700 XT / 7800 XT]
- Driver Version: Mesa 24.3.2-arch1.1

Software information

- Desktop environment: KDE 6.2.5
- Session type: wayland
- Gamescope version: gamescope version 3.16.1 (gcc 14.2.1)
- Gamescope launch command(s): gamescope -W 3440 -H 1440 --hdr-enabled -f --force-grab-cursor -- %command%

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

If needed please let me know where to look. I am happy to provide anything that might help.

@AtmosphericIgnition
Copy link

AtmosphericIgnition commented Jan 3, 2025

I have the same issue on Arch Linux. In my case, I noticed that Red Dead Redemption 2 doesn't register certain keys, which seem to be going to gamescope instead (pressing F toggles fullscreen).

- Distro: Arch Linux
- CPU: 16-core AMD Ryzen 9 5950X
- GPU: NVIDIA RTX 3090
- Driver Version: NVIDIA Open 565.77
- Desktop environment: KDE 6.2.5
- Session type: wayland
- Gamescope version: gamescope version 3.16.1 (gcc 14.2.1)
- Gamescope launch command(s): DXVK_HDR=1 gamemoderun gamescope -f --hdr-enabled -W 3840 -H 2160 -r 240 --force-grab-cursor -- %command%

I solved the issue by going to the Arch Linux pkgbuild repo, cloning it, checking out the 3.15.15-1 tag, building that tag with makepkg, and installing it.

EDIT:
It doesn't seem that EOS modifies their Gamescope release from Arch Linux, in that case, you can try my "fix" by doing:

git clone https://gitlab.archlinux.org/archlinux/packaging/packages/gamescope.git
git checkout 3.15.15-1
makepkg -sri

Afterwards, gamescope --version should show [gamescope] [Info] console: gamescope version 3.15.15 (gcc 14.2.1)

Make sure that no packages other than the build dependencies are being removed when Pacman prompts you for confirmation to install the downgraded version of gamescope. If EOS has their own pkgbuild repo for the gamescope package, you should use that instead of the Arch GitLab I linked.

@juliusmaximus167
Copy link
Author

juliusmaximus167 commented Jan 3, 2025

Replying to #1691 (comment)

Thank you for your comment! I will look into downgrading. Didn't have to do it before, but I guess it's the only option I have if I want to play with hdr.

@AtmosphericIgnition
Copy link

Glad you found it helpful. If the fix works for you, you can also uncomment the IgnorePkg line in /etc/pacman.conf and add the gamescope package to it. This tells Pacman to not update your downgraded gamescope when you update the rest of your system.

Remember to remove gamescope from the line when the issue is fixed in some upcoming release, as the downgraded package might break as it's dependencies update, but you can always just rebuild it if that happens.

@matte-schwartz
Copy link

I fixed this with #1666 but it was merged after 3.16.1 was released so it will be in 3.16.2.

@juliusmaximus167
Copy link
Author

Glad you found it helpful. If the fix works for you, you can also uncomment the IgnorePkg line in /etc/pacman.conf and add the gamescope package to it. This tells Pacman to not update your downgraded gamescope when you update the rest of your system.

Remember to remove gamescope from the line when the issue is fixed in some upcoming release, as the downgraded package might break as it's dependencies update, but you can always just rebuild it if that happens.

You have been very helpful, thank you very much!

I fixed this with #1666 but it was merged after 3.16.1 was released so it will be in 3.16.2.

Thank you for letting me know. I searched for a sticky super key and didn't come across the other issue with just the fullscreen toggle, sorry for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants