Output from simply starting gmplayer : (no file specified )
gmplayer
MPlayer 2:1.0~rc1-0ubuntu8 (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.
MPlayer interrupted by signal 4 in module: unknown
- MPlayer crashed by an 'Illegal Instruction'.
It may be a bug in our new runtime CPU-detection code...
Please read DOCS/HTML/en/bugreports.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/en/bugreports_what.html#bugreports_crash.
- 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/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.
Output from simply starting gmplayer : (no file specified )
gmplayer
MPlayer 2:1.0~rc1-0ubuntu8 (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.
MPlayer interrupted by signal 4 in module: unknown en/bugreports. html. en/bugreports_ what.html# bugreports_ crash. HTML/en/ bugreports. html and follow the instructions there. We can't and
- 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.