GNOME Bugzilla – Bug 792227
Black screen with pixel noise when playing videos with 1.12.4
Last modified: 2018-02-27 13:58:40 UTC
Created attachment 366353 [details] Screenshot When playing videos in Totem with GStreamer 1.12.4, the image is corrupted (see attached picture; audio works fine). The same videos work just fine after downgrading the following packages to 1.12.3: gstreamer gst-plugins-base-libs gst-plugins-bad gst-plugins-base gst-plugins-good gst-libav gst-plugins-ugly gstreamer-vaapi I can observe the above with a number of different .mov and .mp4's. Among others, the issue can be reproduced with this sample mp4 video: https://cloud.blender.org/p/glass-half/5645e616c379cf0386babbf7 Attaching GST_DEBUG=*:6 logs recorded with both GStreamer versions. -- OS: Arch Linux (Antergos) Kernel: 4.14.9-1-ARCH Mesa: 17.3.1 Totem: 3.26.0
Created attachment 366354 [details] GStreamer 1.12.3 log - first few secs of video playback in Totem
Created attachment 366355 [details] GStreamer 1.12.4 log - first few secs of video playback in Totem
Looks like in the 1.12.4 not-working case the VAAPI decoder is used, whereas in the 1.12.3 working case the libav avdec_h264 decoder is used.
I confirm it. clutter-gst when negotiates GLUploadTextureMeta paints that noise in X. I suspect is some recent change in mesa.
And affects 1.12 and master
A work around is to use EGL instead of GLX, exporting these environment variables: $ CLUTTER_DRIVER=gles2 \ GST_GL_PLATFORM=egl totem file.mkv
It seems I have to bisect mesa, to figure out what's happening :(
already done: https://bugs.freedesktop.org/show_bug.cgi?id=105013
Yeah bug 105013 is the same bug as this. I just didn't find this one when I logged it because knowing the regression happened in Mesa, I did not search Gstreamer bugs.
I mean https://bugs.freedesktop.org/show_bug.cgi?id=105013 :)
Thanks a bunch, Daniel! :DD
I've closed this bug since it is related with mesa and not gstreamer-vaapi. But if the problem continues after the mesa's fix, please, reopen it.
*** Bug 793257 has been marked as a duplicate of this bug. ***