desktop-packages team mailing list archive

["if.gnu.linux" <if.gnu.linux@xxxxxxxxx>]

I can confirm that @Eric Piel is right saying that  gstreamer1.0-vaapi
is the culprit. Without gstreamer1.0-vaapi, I can play example.mp4 file
in bug #1373978 without any problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to clutter-gst-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1416005

Title:
  totem fails to play video if gstreamer-vaapi is installed

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in clutter-gst-2.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-2.0 package in Debian:
  New

Bug description:
  If gstreamer-vaapi is installed Totem fails to play anything, and instead just shows an error popup saying "GStreamer encountered a general stream error". The app doesn't produce any error msg on the terminal, but shows that vaapi is being used:
  ...
  (totem:8470): Grilo-WARNING **: [registry] grl-registry.c:472: Could not open plugins' info directory '/usr/lib/x86_64-linux-gnu/grilo-0.2': Error opening directory '/usr/lib/x86_64-linux-gnu/grilo-0.2': No such file or directory

  (totem:8470): Totem-WARNING **: Failed to load grilo plugins: All configured plugin paths are invalid
  libva info: VA-API version 0.37.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_36
  libva info: va_openDriver() returns 0

  (totem:8470): Gtk-WARNING **: Symbolic icon view-sidebar-symbolic-ltr of size 16 is in an icon theme directory of size 128
  ...

  Gst-launch using vaapidecocde and vaapisink still works properly,
  using

  gst-launch-1.0 filesrc location=bbb_sunflower_2160p_60fps_normal.mp4 !
  qtdemux ! vaapidecode ! vaapisink

  takes 6% cpu instead of 300% on my broadwell based laptop.

  video downloaded from here
  http://bbb3d.renderfarming.net/download.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1416005/+subscriptions