Actually, when I remove the symbolic link that I added a few months ago (to get video playback working, and I had forgotten about):
/usr/lib/libx264.so.65 --> /usr/lib/libx264.so.67 I get the error that I first got months ago: ffmpeg: error while loading shared libraries: libx264.so.65: cannot open shared object file: No such file or directory It seems that .65 is not installed by the karmic libx264 or libavcodec packages, yet ffmpeg still tries to link to it. Doing your own symbolic link to the .67 object (as above) works for playback, but evidently not encoding. So this bug becomes "why is ffmpeg pointing to the wrong version of libx264" - which is a duplicate of Bug #474948 (since I'm also running on the amd64 platform) Cheers, J -- ffmpeg segfault regression - working cli encode in jaunty now broken in karmic https://bugs.launchpad.net/bugs/491876 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/universe-bugs
