libfaad.so.0 errors on AAC audio playback in 8.04 Hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mythtv (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mythtv
On 8.04 with the release 0.21 packages I am getting an error playing mp4 videos that have AAC audio.
There seems to be a problem with mythtv loading the the Hardy libfaad library.
When trying to play a video with the internal player or when trying to commflag on I get the following error repeated before the frontend or mythcommflag segfaults:
2008-03-11 12:37:34.920 [mpeg4aac @ 0xb73fa288]FAAD library: cannot resolve faacDecGetError
If I run this on a Gusty system the video plays or commflags fine. If I use LD_LIBRARY_
A (legal) sample video is here (10Megs) : http://
mythcommflag --video 200_KIDNEYS_
gives:
... repeated errors...
2008-03-11 12:45:22.135 [mpeg4aac @ 0xb7382288]FAAD library: cannot resolve faacDecGetError
2008-03-11 12:45:22.136 [mpeg4aac @ 0xb7382288]FAAD library: cannot resolve faacDecGetError
2008-03-11 12:45:22.136 AFD Error: Could not open codec 0x81fd500, id(AAC) type(Audio) aborting. reason -1
2008-03-11 12:45:22.137 NVP: Disabling Audio, params(-1,-1,-1)
Segmentation fault (core dumped)
running with the library set to overload with a gusty libfaad:
LD_
lets the video commflag properly. And the video plays successfully with audio.
On gusty I have libfaad2-0 installed. On hardy that package is a dummy package that has been replaced by libfaad0.
mythtv@mini:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
mythtv@mini:~$ apt-cache policy mythtv libfaad0 libfaad2-0
mythtv:
Installed: (none)
Candidate: 0.21.0-0ubuntu2
Version table:
0.
500 http://
libfaad0:
Installed: 2.6.1-2
Candidate: 2.6.1-2
Version table:
*** 2.6.1-2 0
500 http://
100 /var/lib/
libfaad2-0:
Installed: 2.6.1-2
Candidate: 2.6.1-2
Version table:
*** 2.6.1-2 0
500 http://
100 /var/lib/
Related branches
Changed in mythtv: | |
status: | New → Fix Committed |
My suspicion is that this is caused by libfaad-bin in our build flags. I'll do some experimentation.