[Bug 789473] vaapi plugins removed from registry at early boot

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=789473

Florent Thiéry <florent.thiery at ubicast.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #17 from Florent Thiéry <florent.thiery at ubicast.eu> ---
jackpot, when it fails:

# systemctl status vaapi
● vaapi.service - Vaapi early boot test
   Loaded: loaded (/usr/lib/systemd/system/vaapi.service; enabled; vendor
preset: disabled)
   Active: inactive (dead) since Thu 2018-03-29 18:08:05 CEST; 26s ago
  Process: 308 ExecStart=/usr/local/bin/vaapi.sh (code=exited,
status=0/SUCCESS)
 Main PID: 308 (code=exited, status=0/SUCCESS)

Mar 29 18:08:05 mediacoder-i3 vaapi.sh[308]: 2.48 5.93
Mar 29 18:08:05 mediacoder-i3 vaapi.sh[308]: ls: cannot access '/dev/dri': No
such file or directory
Mar 29 18:08:05 mediacoder-i3 systemd[1]: Started Vaapi early boot test.
Mar 29 18:08:05 mediacoder-i3 vaapi.sh[308]: 2.73 6.06

I tried a lot of things with systemd, but none that would allow me to still
start the service on a system that does not have a GPU, so i ended up adding an
exec start pre condition waiting for /dev/dri/card0 and timing out after a
delay.

I am closing this as this is not really gstreamer's fault...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.