Comment 2 for bug 1642901

Thanks for taking the time to explain. I had an older backup restored,
which brought an obsolete ffmpeg version into ~/bin. This gave the false
alarm, because ~/bin had priority in my PATH. Sorry for causing unnecessary
work.

Erik

Andreas Cadhalpun <email address hidden> schrieb am Sa., 19. Nov.
2016 um 00:27 Uhr:

> I've just verified that ffmpeg 3.2-2 from zesty starts fine after
> installation in a minimal chroot.
> Your problem is caused by third-party libraries.
> To identify the problematic one, try running the following command:
> $ for lib in $(ldd /usr/bin/ffmpeg | sed 's/.*=> \(.*\) (.*/\1/'); do [ -e
> "$lib" ] && ldd "$lib" | grep libSDL && echo "$lib"; done
> libSDL2-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0
> (0x00007f2c0db1e000)
> /usr/lib/x86_64-linux-gnu/libavdevice.so.57
>
> As you can see, there is no libSDL1.2 here thus I'm closing this bug as
> invalid.
>
> ** Changed in: ffmpeg (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1642901
>
> Title:
> ffmpeg dependent on libSDL-1.2.so.0 instead libsdl2-2.0-0
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1642901/+subscriptions
>