After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793376 - vaapisink: disable for autoplugging?
vaapisink: disable for autoplugging?
Status: RESOLVED DUPLICATE of bug 775698
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-12 09:46 UTC by Tim-Philipp Müller
Modified: 2018-02-12 16:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2018-02-12 09:46:29 UTC 
On debian/sid, gnome-shell on wayland:

gst-play-1.0 $anything

wl_surface@7: error 2: Failed to create a texture for surface 7: Unsupported buffer format 12760
0:00:10.807996216 17794 0x7f10940580f0 ERROR                  vaapi gstvaapiwindow_wayland.c:211:gst_vaapi_window_wayland_sync: Error on dispatching events: Protocol error

Sometimes:

0:00:02.002503390 25405 0x7f20d80d6a80 ERROR                  vaapi gstvaapiwindow_wayland.c:211:gst_vaapi_window_wayland_sync: Error on dispatching events: Broken pipe
ERROR Internal error: could not render surface for file:///home/tpm/samples/misc/bbcnews.m2t
ERROR debug information: gstvaapisink.c(1475): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
0:00:02.002808856 25405 0x7f20d811c2d0 ERROR        subtitleoverlay gstsubtitleoverlay.c:1635:gst_subtitle_overlay_src_proxy_chain:<suboverlay> Downstream chain error: error
Comment 1 Víctor Manuel Jáquez Leal 2018-02-12 11:07:34 UTC 
Yeah, as it hardly will be a patch for cogl, to support YUV, neither in vaapi to export RGB instead of NV12, the idea is to demote vaapisink when WAYLAND_DISPLAY is exported.

But let's keep the discussion in #775698

*** This bug has been marked as a duplicate of bug 775698 ***