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 755354 - Totem displays black screen on Wayland with libva-intel
Totem displays black screen on Wayland with libva-intel
Status: RESOLVED NOTABUG
Product: gstreamer-vaapi
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gstreamer-vaapi maintainer(s)
gstreamer-vaapi maintainer(s)
Depends on:
Blocks: 748634
 
 
Reported: 2015-09-21 14:37 UTC by František Zatloukal
Modified: 2015-11-19 17:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description František Zatloukal 2015-09-21 14:37:02 UTC 
Totem is working without any issues on Wayland by default (log with VA-API driver missing):
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 1
libva error: va_getDriverName() failed with operation failed,driver_name=i965

After installing VA-API driver to enable VA-API video acceleration, totem won't work correctly:
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_37
libva info: va_openDriver() returns 0

VA-API driver is installed and loaded but works correctly only on X session. Black window is the only output displayed on Wayland session.

Driver package: libva-intel-driver-1.5.1-1.fc22.x86_64.rpm
GPU: Bay Trail Intel HD Graphics
Totem 3.17.92
Comment 1 Bastien Nocera 2015-09-21 14:48:03 UTC 
gst-vaapi probably doesn't work with Wayland (or with clutter-gst under Wayland).
Comment 2 František Zatloukal 2015-09-21 16:24:54 UTC 
So in this case it would be better to disable va-api support when launched on Wayland IMO.
Comment 3 Víctor Manuel Jáquez Leal 2015-09-21 16:36:55 UTC 
As far as I have tested, gstreamer-vaapi works well in wayland/weston using vaapisink. walyandsink won't work. I haven't tested with clutter-gst.
Comment 4 Víctor Manuel Jáquez Leal 2015-11-19 16:37:21 UTC 
František,

Could you attach a debug log to the log? GST_DEBUG=*:3,*clutter*:5,vaapi*:5 

More info about debug log messages:

https://wiki.gnome.org/Apps/Videos/BugReporting
Comment 5 Víctor Manuel Jáquez Leal 2015-11-19 16:40:49 UTC 
As a side note:

Running cogl/clutter/clutter-gst3 from jhbuild with gstreamer-vaapi won't work because clutter-gst3 uses OpenGL3, and it is not supported by gstreamer-vaapi right now. That's why I asked for the logs, to confirm the reason. 

See bug 753099
Comment 6 František Zatloukal 2015-11-19 16:55:45 UTC 
I've tested it again on updated Fedora 23 (Totem 3.18.1) and everything works correctly now. So I suppose it's not necessary to send log?
Comment 7 Víctor Manuel Jáquez Leal 2015-11-19 17:07:28 UTC 
(In reply to František Zatloukal from comment #6)
> I've tested it again on updated Fedora 23 (Totem 3.18.1) and everything
> works correctly now. So I suppose it's not necessary to send log?

Glad to hear that! And let's close this bug.