GNOME Bugzilla – Bug 796033
Totem window is all black in Wayland sessions on Sandy Bridge (and Clarkdale) CPUs
Last modified: 2018-11-03 15:54:21 UTC
Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1770725 Regards, -- Cristian Aravena Romero (caravena)
Hello, - Not work wity Wayland - Work with Xorg Regards, -- Cristian Aravena Romero (caravena)
Please extract and summarize the bug information. This will save time to volunteer looking at your report. This will also make Triaging possible. We deal with a lot of bug report, this will help the bug be addressed sooner.
Created attachment 371945 [details] $dpkg -l | grep ayland
Thanks for taking the time to report this. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read https://bugzilla.gnome.org/page.cgi?id=bug-writing.html and add a more useful description to this bug. When providing a better description, please reset the status of this bug report from NEEDINFO to its previous status.
Maybe wait till we've collected some basic info in the downstream bug: https://launchpad.net/bugs/1770725
Summary from Launchpad: Using a Sandy Bridge CPU, which supports H.264 High Profile (according to vainfo), gstreamer1.0-vaapi accelerated playback works in Xorg sessions, but not Wayland sessions. The problem, I guess, is that the EGL path might be using some features not available on Sandy Bridge (like half precision floats, or other shader/GL features).
I have now verified the bug with my own hardware. It only occurs on a Sandy Bridge CPU in Wayland sessions (EGL). After moving the hard drive into an Ivy Bridge machine it then works. So the problem is specific to Sandy Bridge + EGL.
I wonder if this is the problem: gstvaapiwindow_egl.c: static const gchar *vert_shader_text = "#ifdef GL_ES \n" "precision mediump float; \n" ... static const gchar *frag_shader_text_rgba = "#ifdef GL_ES \n" "precision mediump float; \n" If mediump equates to 16-bit (half precision) floats on Intel, then those shaders won't work on pre-Ivy Bridge CPUs.
Would be really nice to change that and see if you can get it working somehow.
Furthermore I can confirm the bug occurs with: clutterautovideosink glimagesink but does not happen with: ximagesink xvimagesink So that suggests the problem is localized to GL. Sorry I can't afford more time on this bug right now.
Hello, How can I help with this? Regards, -- Cristian Aravena Romero (caravena)
Hello, The report is marked with 'Status: NEEDINFO'. What information do you need to add/correct this request? Best regards, -- Cristian Aravena Romero (caravena)
Thanks! -- Cristian Aravena Romero (caravena)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/95.