backends: Fall back to the default and not the unknown color space

The unknown color space's only purpose is to signal that the current KMS
state has a unknown color space set. It is not one of the color spaces
that can be set. We already only try to set a color space if the default
color space is supported so we should use the default color space as a
fallback instead of the unknown color space.

Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2693
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2915>
This commit is contained in:
Sebastian Wick 2023-03-15 13:28:52 +01:00 committed by Marge Bot
parent 1be2f635e9
commit 3988f5a47f
2 changed files with 3 additions and 3 deletions

View File

@ -520,7 +520,7 @@ ensure_hdr_settings (MetaMonitorManager *manager)
meta_monitor_get_display_name (monitor), error->message);
meta_monitor_set_color_space (monitor,
META_OUTPUT_COLORSPACE_UNKNOWN,
META_OUTPUT_COLORSPACE_DEFAULT,
NULL);
continue;
@ -535,7 +535,7 @@ ensure_hdr_settings (MetaMonitorManager *manager)
meta_monitor_get_display_name (monitor), error->message);
meta_monitor_set_color_space (monitor,
META_OUTPUT_COLORSPACE_UNKNOWN,
META_OUTPUT_COLORSPACE_DEFAULT,
NULL);
meta_monitor_set_hdr_metadata (monitor, &(MetaOutputHdrMetadata) {
.active = FALSE,

View File

@ -626,7 +626,7 @@ meta_output_init (MetaOutput *output)
MetaOutputPrivate *priv = meta_output_get_instance_private (output);
priv->backlight = -1;
priv->color_space = META_OUTPUT_COLORSPACE_UNKNOWN;
priv->color_space = META_OUTPUT_COLORSPACE_DEFAULT;
priv->hdr_metadata.active = FALSE;
}