diff options
author | Sebastian Wick <sebastian.wick@redhat.com> | 2023-03-15 13:28:52 +0100 |
---|---|---|
committer | Marge Bot <marge-bot@gnome.org> | 2023-03-20 10:00:36 +0000 |
commit | 3988f5a47fdff05aa71d92a1741ab3cad725b375 (patch) | |
tree | 31da747825856a35529b8872d2e15cb9362e377c /src/backends/meta-monitor-manager.c | |
parent | 1be2f635e9b61ec6f3ae9184f1b8d94dfffc4c9c (diff) | |
download | mutter-3988f5a47fdff05aa71d92a1741ab3cad725b375.tar.gz |
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>
Diffstat (limited to 'src/backends/meta-monitor-manager.c')
-rw-r--r-- | src/backends/meta-monitor-manager.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backends/meta-monitor-manager.c b/src/backends/meta-monitor-manager.c index 28cc457e7..bd02c55bb 100644 --- a/src/backends/meta-monitor-manager.c +++ b/src/backends/meta-monitor-manager.c @@ -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, |