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

[Bug]: Applications will fail to launch with FSR and gamescope. #3065

Closed
Equivocal90 opened this issue Sep 1, 2023 · 1 comment · Fixed by #3217
Closed

[Bug]: Applications will fail to launch with FSR and gamescope. #3065

Equivocal90 opened this issue Sep 1, 2023 · 1 comment · Fixed by #3217
Labels

Comments

@Equivocal90
Copy link

Describe the bug

Applications immediately exit if launched with FSR and gamescope enabled.

I'm pretty certain this is because gamescope changed the argument for FSR and no longer recognizes the old one.

Running app in terminal shows the below.

gamescope-brokey: invalid option -- 'U' See --help for a list of options.

To Reproduce

  1. Enable both FSR and Gamescope.
  2. Launch app
  3. App exits immediately.

Package

Flatpak from Flathub

Distribution

Fedora 38

Debugging Information

Official Package: true
Version: '51.9'
DE/WM: gnome
Display:
    X.org: true
    X.org (port): :0
    Wayland: true
Graphics:
    vendors:
        amd:
            vendor: amd
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/radeon_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/radeon_icd.i686.json
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.3.11-200.fc38.x86_64
Disk:
    Total: 16777814016
    Free: 16777662464
RAM:
    MemTotal: 31.3GiB
    MemAvailable: 25.6GiB
Bottles_envs: null

Troubleshooting Logs

No response

Additional context

No response

@orowith2os
Copy link
Contributor

I'm pretty certain this is because gamescope changed the argument for FSR and no longer recognizes the old one.

This is indeed the case. Some movement on #2840 should fix it up, hopefully.

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

Successfully merging a pull request may close this issue.

2 participants