`error 0: Windows scRGB is not supported` on GNOME, Hyprland

[Lawstorant]

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

AS of cb3fdea gamescope is broken. Tested as standalone session and in Gnome 48.

libdecor is installed and plugins are in system.

Steps To Reproduce

Run anything with gamescope from current master

Hardware information

- Distro: Arch Linux
- CPU: Ryzen 7 5800X3D
- GPU: Radeon 9070 XT
- Driver Version: 25.0.4

Software information

- Desktop environment: Gnome 48
- Session type: wayland
- Gamescope version: https://github.com/ValveSoftware/gamescope/commit/cb3fdea3e4c000f4a1d618b3826d44fd0cbeaafe
- Gamescope launch command(s): gamescope

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

gamescope_crash.log

[matte-schwartz]

i could reproduce this on gnome earlier but was waiting for that original reporter to file an issue, it seems to be 8a3864f

kde is fine however

[effects3d]

This also occurs on the latest release of Hyprland with the same error.

[LionHeartP]

This also occurs on the latest release of Hyprland with the same error.

On Hyprland you can do debug:full_cm_proto=true to trick gamescope into thinking Hyprland supports windows scRGB, then with the --hdr-debug-force-output option it will work, although it appears to be using Frog CM instead of Upstream.

[Lawstorant]

@misyltoad is scRGB support necessary for gamescope?

[misyltoad]

Yes

[Lawstorant]

OK, created mutter issue https://gitlab.gnome.org/GNOME/mutter/-/issues/4083

[effects3d]

On Hyprland you can do debug:full_cm_proto=true to trick gamescope into thinking Hyprland supports windows scRGB, then with the --hdr-debug-force-output option it will work, although it appears to be using Frog CM instead of Upstream.

It just worked after enabling that Hyprland debug option. Running it with --hdr-debug-force-output wasn't necesary.

[FooBarrior]

Running into this issue as well, on Gnome/mutter.
As I understood, it's related to HDR color management. Following I tried to enable HDR for my monitor, and that didn't help.

Is there any workaround one may apply to make it run under mutter?
E.g. run into a nested compositor, or enable/disable gamescope hdr?

Would be great to have some instruction's 'cause it doesn't seem to be resolved fast.

[Lawstorant]

The two possible resolutions are:

1. Muter implements the get_windows_scrgb()
2. Gamescope uses a workaround when get_windows_scrgb() is not available.