brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

wayland/buffer: Avoid spamming the log when a buffer is not scanoutable

Browse Source 
It's not really an error and we recover seamlessly.

If someone really wants to check if/why direct scanout is failing then
they can still use `env MUTTER_DEBUG=render,kms`.

Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2702
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2918>
This commit is contained in:
Daniel van Vugt 2023-03-16 18:16:13 +08:00
parent 176418d0e7
commit 46e1ede687
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/wayland/meta-wayland-buffer.c
View File

@ -877,8 +877,7 @@ meta_wayland_buffer_try_acquire_scanout (MetaWaylandBuffer *buffer,
return NULL; return NULL;
} }
g_return_val_if_fail (scanout, NULL); if (scanout)
g_signal_connect (scanout, "scanout-failed", g_signal_connect (scanout, "scanout-failed",
G_CALLBACK (on_scanout_failed), buffer); G_CALLBACK (on_scanout_failed), buffer);