bazzite: Streaming (Sunshine or Steam Link) does not capture Steam UI
Describe the bug
Right now, when streaming to another machine using Steam Link or sunshine, I cannot get the remote machine to see the Steam UI - it is simply not rendered in the stream.
That is, if I am playing a game:
…and I hit the Steam button (or equivalent mapped to my remote controller), I will see this on the machine’s physical display (captured with a PiKVM):
…and after pressing “down”, the UI becomes translucent:
However, sunshine/Moonlight/Steam Link will display none of it. On the client machine will always see the game layer, without anything overlaid (although I can hear the UI audio):
I have tried Steam Link settings, checked If sunshine is running with setcap, and also tried a number of different images (see #1260 to get an idea), but the issue happens on both deck and non-deck images, on GNOME or KDE.
Am curious to understand if this is a Wayland or AMD thing and if there are any fixes/workarounds.
What did you expect to happen?
I expected the stream to match the physical display.
Output of rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:40-stable-20240611
Digest: sha256:26b268ec5de0c1618f0618855761b2da934614dfb060fd5d69ffed4fad14d2b9
Version: 40.20240611.0 (2024-06-11T16:59:32Z)
Diff: 460 removed, 193 added
LayeredPackages: fio python3.11 python3.11-devel sunshine
Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable-20240611
Digest: sha256:6c59a228186bdbd3417580129702a9337c2edadac0206b0d4773df53dca58413
Version: 40.20240611.0 (2024-06-11T17:01:53Z)
LayeredPackages: fio python3.11 python3.11-devel sunshine
Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:40-stable-20240611
Digest: sha256:26b268ec5de0c1618f0618855761b2da934614dfb060fd5d69ffed4fad14d2b9
Version: 40.20240611.0 (2024-06-11T16:59:32Z)
LayeredPackages: fio python3.11 python3.11-devel sunshine
Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/deck-blacklist.conf"'
Hardware
me@bazzite
%%%%%%====%%%%%%%%%%
%%%%%%%% %%%%%%%%%%%%%% bazzite-deck:stable
%%%%%%%%% %%%%%%%%%%%%%%%% Fedora Linux 40 (Kinoite) x86_64
%%%%%%%%% %%%%%%%%%%%%%%%### Linux 6.8.12-301.fsync.fc40.x86_64
%%%%%%%%% %%%%%%%%%%%%%###### 2 hours, 30 mins
== =======###### Spawned on Feb 27 2024
== =========#####
%%%%%%%%% %%%%%%%####======##### HCAR6000-MI2
%%%%%%%%% %%%%%#######=====##### AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16) @ 6.08 GHz
%%%%%%%%% %%%#########=====##### AMD Radeon 780M @ 0.80 GHz [Integrated]
%%%%%%%%% %%##########=====##### 5.15 GiB / 30.60 GiB (17%)
%%%%%%%%%====###########=====###### 384.69 GiB / 475.35 GiB (81%) - btrfs [Read-only]
%%%%%%%%====#########======###### 1920x1080 @ 50Hz [External]
%%%%%%%=====#####========###### PiKVM Composite KVM Device
%%%%###===============####### Mouse passthrough
%#######==========#########
####################### bash 5.2.26
################### /dev/pts/1
########### 2717 (rpm), 79 (flatpak-system), 41 (flatpak-user)
● ● ● ● ● ● ● ●
Extra information or context
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 9
- Comments: 37 (1 by maintainers)
Update:
On my test system, I’ve bisected the bug to two components, it takes the right combination of versions for the bug to appear/disapper:
For gamescope, this commit is where the bug first shows up: https://github.com/ValveSoftware/gamescope/commit/04ad0c9be89cfa2a4152908fd2bfe16743591757 titled:
drm: Update AMD color management for Linux 6.8. This commit was reverted for several releases after it was introduced. Finally, it was permanently present in releasev3.14.8and later. The latest release where the bug does NOT reproduce isv3.14.7.Technically my bisect was done against ChimeraOS’s fork of Gamescope called
gamescope-plus, where this screenshot comes from. Chimera keeps it’s fork up to date, and any build from these commits exactly matches Valves official repo. Note, I marked commits with branch namesworkingandbrokento indicated which commits contain the undesired behavior:For the kernel, I’m using ChimeraOS’s kernel. My bisect located two boundaries. Essentially, the bug appears in version
v6.6.4-chos2-2and earlier, goes away fromv6.6.4-chose3-1tov6.6.17-chos2-1. Finally the bug reappears in all theirv6.8.xbuilds and later. See screenshot with my branches markedbuggedvsworksto see what I tested. For this, I haven’t nailed down the actual kernel commits. I looked into it and the diff is hard to make sense of. I plan to better bisect this as I have time.Bottom line, the bug GOES AWAY when these two conditions are met:
Gamescopeorgamescope-plusversion isv3.14.7or earlier.v6.6.4-chos3-1tov6.6.17-chos2-1Any combination outside those versions will contain this sunshine overlay bug.
For now, to work around this bug, I’m using the Arch community mirror archive to back-date my Arch install to
Apr 11, 2024, and running ChimeraOS kernelv6.6.17-chos2-1, with gamescope-plusv3.14.7, and all the gamescope session related packages, to make it boot directly into game mode.Amazing work @nlflint !
Really hoping that this infuriating bug can be fixed soon
I opened a bug issue over at the Sunshine Github: https://github.com/LizardByte/Sunshine/issues/3860
Update: I was able to make the bug go away on Arch, but I had to take some extreme measures to do it:
I’m going bisect this stuff until I can narrow down the problem. Probably gonna take awhile. However, it does seem kernel related after all, as just changing to a regular kernel (non-chimeraos, but same version) brings the bug back.
@bugs181 @chunky-games
None of those workarounds made a difference on my machine (I’m on arch, so maybe because I have slightly different package versions). I tried playing around with more Steam display settings, and QAM settings, and nothing fixed it but…
Enabling HDR fixes it! (for the most part). I have a new overlay issue with one of my games, but the overlays work as expected in all the other games I tested. HDR looks great on my livingroom TV w/AppleTV4k. However, it’s not a permanent fix as I have a client w/o an HDR monitor and the colors are messed up when in HDR.
This is with the latest packages and kernel as of today on Arch.
I have this Problem with Sunshine -> Moonlight, or Steam Remote Play -> Windows Steam Remote Play on my Bazzite Machine, and from my Steam Deck (Official Steam OS) ->Windows Steam Remote Play. On the Homescreen of Gamescope it is working, but not when starting a game.
rpm-ostree status: State: idle Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable Digest: sha256:308783769ddf7450b76837670cfb4eef915f42b04fca85d6c18efe67e289d78c Version: 42.20250708.1 (2025-07-09T00:37:02Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable Digest: sha256:e7efe7a4715cfa4f74573954245019db49942ae13fd33487a77b43622b9ba435 Version: 42.20250708 (2025-07-08T05:41:28Z)
My Bazzite Machine has an RX 6700 XT.
Another workaround reported by someone: https://github.com/LizardByte/Sunshine/issues/3860#issuecomment-2954267416
I sort of have this also, but however using mouse mode via Xbox controller brings the overlay up or move the mouse via my iPad also fixes this but when the mouse hides so does the overlay
Don’t think this is something we can fix as i vaguely remember this also being a problem on SteamOS