While I do realise that the gst-plugins-libav ebuild is theoretically only applicable to libav and that ffmpeg is 'not entirely supported' upstream, it is perfectly functional using ffmpeg instead of libav. The problem happens when ffmpeg is upgraded, for instance 2.3 on 27 July. When I upgraded ffmpeg, applications using gst-plugins-libav - such as Firefox's gstreamer support for HTML5, and Pidgin's incoming sound notificatiosn - would receive segfaults when trying to play audio due to subtle ABI changes in the library. This was resolved with a simple rebuild of gst-plugins-libav. I believe therefore that ffmpeg should trigger a rebuild of gst-plugins-libav if it is installed. Reproducible: Always Steps to Reproduce: 1. emerge ffmpeg-2.2.5 gst-plugins-libav 2. upgrade ffmpeg to 2.3 3. attempt to use gstreamer client such as Firefox HTML5 Actual Results: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2d098ff700 (LWP 20211)] (gdb) where #0 0x00007f2d3efecbfb in gst_ffmpegdemux_register () from /usr/lib64/gstreamer-1.0/libgstlibav.so #1 0x00007f2d3efd0e25 in plugin_init () from /usr/lib64/gstreamer-1.0/libgstlibav.so #2 0x00007f2d1646c45b in gst_plugin_register_func () from /usr/lib64/libgstreamer-1.0.so.0 Expected Results: Ability to listen to my cat videos on YouTube and aural notification of IMs in Pidgin.
Please post your `emerge --info media-plugins/gst-plugins-libav' output in a comment.
This is (IMHO) more of an upstream failure on ffmpeg side. *** This bug has been marked as a duplicate of bug 518338 ***
