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 743225 - vaapipostproc: clear state on stop
vaapipostproc: clear state on stop
Status: RESOLVED FIXED
Product: gstreamer-vaapi
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gstreamer-vaapi maintainer(s)
gstreamer-vaapi maintainer(s)
Depends on:
Blocks: 731852
 
 
Reported: 2015-01-20 08:23 UTC by Michael Olbrich
Modified: 2015-01-27 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (1.11 KB, patch)
2015-01-20 08:23 UTC, Michael Olbrich 		none Details | Review

Description Michael Olbrich 2015-01-20 08:23:56 UTC 
Created attachment 294954 [details] [review]
patch

Otherwise restarting may fail because the state of vaapipluginbase and
vaapipostproc don't match.
e.g. gst_vaapipostproc_set_caps() will skip initailization and not call
gst_vaapi_plugin_base_set_caps()
Comment 1 Víctor Manuel Jáquez Leal 2015-01-20 08:29:50 UTC 
Review of attachment 294954 [details] [review]:

LGTM.
Comment 2 sreerenj 2015-01-27 14:09:55 UTC 
Pushed, Thanks for the patch and review.

commit 22d1acb6d2f754fb851bd0f2fc535adf81b37d0b
Author: Michael Olbrich <m.olbrich@pengutronix.de>
Date:   Tue Jan 27 16:06:02 2015 +0200

    vaapipostproc: clear state on stop
    
    Otherwise restarting may fail because the state of vaapipluginbase and
    vaapipostproc don't match. e.g. gst_vaapipostproc_set_caps() will skip
    initailization and not call gst_vaapi_plugin_base_set_caps()