bazzite: gamescope bug: Game mode now always uses highest possible refresh rate, ignores user set display settings

Describe the bug

I noticed a bug in Bazzite deck stable image on two separated computers where in game mode the display will always operate at highest possible refresh rate of given resolution regardless of choosen refresh rate.

Setup 1: Ryzen 9800x3D with Sapphire Pulse 9070 xt GPU, 4k Samsung TV connected over HDMI to the GPU, the TV supports 120, 100 and 60 Hz modes at 4k

Setup 2: Ryzen 5800x3D with AMD reference 6950 xt GPU, 4k Alienware monitor connected over Displayport 1.4 to laptop docking station and the docking station connected to PC over USB-C cable, right into GPU.

Both machines have the Bazzite deck image on stable branch. When booted into game mode, with automatic resolution disabled it allow one to choose resolution to use.

Setup 1:

  • When setting resolution from the list to 3840x2160@120 it operates at 120 Hz (correct)
  • When setting resolution from the list to 3840x2160@100 it operates at 120 Hz (incorrect)
  • When setting resolution from the list to 3840x2160@60 it operates at 120 Hz (incorrect)

Setup 2:

  • When setting resolution from the list to 3840x2160@144 it operates at 144 Hz (correct)
  • When setting resolution from the list to 3840x2160@120 it operates at 120 Hz (incorrect)
  • When setting resolution from the list to 3840x2160@60 it operates at 120 Hz (incorrect)

The actual refresh rate has been confirmed by TV and monitor’s built in OSD as well as right-side quick access menu in game mode. When setting the performance overlay to full view it also reports respectivly 120 Hz and 144 Hz instead of the set values.

When changing the refresh rate from resolution list it does not flicker but instantly ask if the new settings are okay and if I want to keep those new settings. Rebooting the computers does not resolve it.

Rebooting into desktop mode and checking the monitor’s and TV OSDs does show correct refresh rate exactly as set in the desktop mode’s display settings. It seems to be a bug within game mode. It used to work about 2 weeks ago, both of those computers have been now updated for the first time in about 2 weeks.

What did you expect to happen?

I expected the refresh rate to be reduced to choosen variable

Output of rpm-ostree status

Setup 1:
# rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:6f8bbe709d2fa6a7c0094c2f02012d097fd3a59e235033f70807668acfe5b7fc
                  Version: 42.20250511 (2025-05-12T03:51:16Z)
          LayeredPackages: htop mpv

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:5a7243860ed83ea6accb3845ba8948a06ee344163cb4696d6fe79b95abad25e9
                  Version: 42.20250430 (2025-05-01T19:27:27Z)
          LayeredPackages: htop mpv

Setup 2:
# rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:38ef326fd9608171ec85b1fef019bcd3d1883041832e5f5134f93c51db262a7c
                  Version: 42.20250513 (2025-05-13T16:20:32Z)
          LayeredPackages: htop mpv
            LocalPackages: lact-0.6.0-0.x86_64

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:bd13f05f33bd1003b37ff5f3d34e031f99f28f31be1324c44e415f4556b6b45b
                  Version: 42.20250425 (2025-04-25T16:42:58Z)
          LayeredPackages: htop mpv
            LocalPackages: lact-0.6.0-0.x86_64

Hardware

Setup 1: Ryzen 9800x3D with Sapphire Pulse 9070 xt GPU, 4k Samsung TV connected over HDMI to the GPU, the TV supports 120, 100 and 60 Hz modes at 4k

Setup 2: Ryzen 5800x3D with AMD reference 6950 xt GPU, 4k Alienware monitor connected over Displayport 1.4 to laptop docking station and the docking station connected to PC over USB-C cable, right into GPU.

Extra information or context

Since I was able to reproduce it on two much different computers I would suspect it is reproducible bug.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16

Most upvoted comments

It’s gamescope. We updated it to the new version that has some new timing stuff. It must have broken external display resolution

You can have a look here: https://github.com/bazzite-org/gamescope

The directory includes a sync.sh script you can use to test your changes on bazzite

Thanks! I’ve done a git bisect and tested on my system. The commit that broke it is https://github.com/bazzite-org/gamescope/commit/c02b489406ac13b8fc5fd93e74289e243c180237

We fixed the other issues. Not this one. The last version is on bazzite

FYI: I rolled back to 42.20250417 and the issue disappeared: I can set the display mode in Steam display settings and it honors what I have chosen. I will now do a bisection and check exactly what version of Bazzite introduced this regression.