mplayer fails to decode mp3 audio on ppc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mplayer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mplayer
with a currently up-to-date feisty install on a pbook:
$ cat /proc/cpuinfo
processor : 0
cpu : 7447A, altivec supported
clock : 833.333000MHz
revision : 0.5 (pvr 8003 0105)
bogomips : 16.57
timebase : 8320000
platform : PowerMac
machine : PowerBook5,8
motherboard : PowerBook5,8 MacRISC3 Power Macintosh
detected as : 287 (PowerBook G4 15")
pmac flags : 00000019
L2 cache : 512K unified
pmac-generation : NewWorld
ii mplayer 1.0~rc1-0ubuntu3 The Ultimate Movie Player For Linux
seems to have problems playing videos with mp3 audio streams, or even any mp3 audio file I could find:
(a self compiled mplayer from svn would work flawless...)
$ /usr/bin/mplayer test.mp3
MPlayer 2:1.0~rc1-0ubuntu3 (C) 2000-2006 MPlayer Team
AltiVec found
CPU: PowerPC
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing test.mp3.
Audio file file format detected.
=======
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
MPlayer interrupted by signal 4 in module: init_audio_codec
- MPlayer crashed by an 'Illegal Instruction'.
It may be a bug in our new runtime CPU-detection code...
Please read DOCS/HTML/
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/
won't help unless you provide this information when reporting a possible bug.
There's unfortunately not much we can do without a backtrace from GDB. Can you please follow the instructions in the error message, and obtain a backtrace?