Ah. It seems for some reason, they were all pointing at old versions.
After a few ln -sf operations it's now working. Question is, how did it
happen??? A mystery. Cheers for you help though.
--
Missing dependency libx264.so.65 on amd64 platform
https://bugs.launchpad.net/bugs/474948
You received
The ldd outputs are completely different - see attachment. How can this
be when the md5sum on /usr/bin/ffmpeg and /usr/lib/libavcodec.so.52 are
the same?
** Attachment added: ldd output from broken machine and new karmic install
http://launchpadlibrarian.net/38054967/ldd-output.txt
--
On Mo, Jan 18, 2010 at 21:34:32 (CET), Jonathan Harker wrote:
The ldd outputs are completely different - see attachment. How can this
be when the md5sum on /usr/bin/ffmpeg and /usr/lib/libavcodec.so.52 are
the same?
ldd resolves the dependencies recursively. It uses 'objdump -p $file |
grep
Hi, I'm getting the following message when I try to encode video with
ffmpeg in karmic on amd64:
ffmpeg: error while loading shared libraries: libx264.so.65: cannot open
shared object file: No such file or directory
See Bug #491876
** Also affects: ffmpeg
Importance: Undecided
Status:
Specifically, when I symlink 65 to 67 to try a work-around, ffmpeg
segfaults, so the reason becomes ffmpeg (or is it libavcodec-extras) is
pointing to libx264-65 which is the wrong version, as karmic is
libx264-67.
--
Missing dependency libx264.so.65 on amd64 platform
surely not a problem in the ffmpeg package.
** Changed in: ffmpeg
Status: New = Invalid
--
Missing dependency libx264.so.65 on amd64 platform
https://bugs.launchpad.net/bugs/474948
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
seems like libx264 has been updated from libx264-65 (in jaunty) -
libx264-67. however, it seems that mediatomb does not link against
libx264 after all.
Ah, now I see why ffmpeg has a bugtask here.
Please state the *exact* versions of ffmpeg related packages that you
have installed. I'm
Hi Reinhard,
Interesting. Here are the packages I have (on the original amd64 machine I
reported from):
$ dpkg -l|grep ffmpeg
ii ffmpeg 4:0.5+svn20090706-2ubuntu2
multimedia player, server and encoder
ii ffmpeg2theora
On Mo, Jan 18, 2010 at 02:55:44 (CET), Jonathan Harker wrote:
I cannot reproduce this on my work amd64 machine, or my i386 karmic
laptop, but these were freshly installed with karmic, so I wonder if
something went horribly wrong somewhere in the jaunty-karmic upgrade?
that would be possible.
I also had much the same issue when I updated my mythbuntu 9.04
installation to 9.10, however it is not limited to mediatomb, it also
affects other packages that depend on libx264, it also happened to me
with mplayer, I couldn't get it resolved properly (linking would have
worked but I don't like
10 matches
Mail list logo
