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

Flatpak 0.21 disables VRR #1846

Closed
3 tasks done
jdancouga opened this issue Nov 15, 2023 · 2 comments
Closed
3 tasks done

Flatpak 0.21 disables VRR #1846

jdancouga opened this issue Nov 15, 2023 · 2 comments
Labels

Comments

@jdancouga
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your issue described in the documentation?

  • I have read the documentation

Is your issue present in the nightly release?

  • This issue is present in the nightly release

Describe the Bug

Variable Refresh Rate (VRR) is not working if sunshine 0.21 Flatpak version is running. VRR will work again if the sunshine service is killed. This behavior is not observed in 0.21 deb (ubuntu 22.04) package install nor Flatpak 0.20 version.

Expected Behavior

VRR should not be disabled by sunshine service

Additional Context

No response

Host Operating System

Linux

Operating System Version

Mint 21.2 Cinnamon Edition

Architecture

64 bit

Sunshine commit or version

0.21

Package

Linux - flatpak

GPU Type

AMD

GPU Model

Radeon 6800XT

GPU Driver/Mesa Version

Mesa 23.2.1

Capture Method (Linux Only)

X11

Config

hevc_mode = 0
min_log_level = 2
resolutions = [
    352x240,
    480x360,
    858x480,
    1280x720,
    1920x1080,
    2560x1080,
    3440x1440,
    1920x1200,
    3860x2160,
    3840x1600
]
min_threads = 6

Apps

No response

Relevant log output

NA
@jdancouga jdancouga changed the title Flatpak 0.21 disablles VRR Flatpak 0.21 disables VRR Nov 15, 2023
@LizardByte-bot
Copy link
Member

It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!

@LizardByte-bot
Copy link
Member

This issue was closed because it has been stalled for 10 days with no activity.

@LizardByte-bot LizardByte-bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants