[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

problèmes mplayer



Bonjour à tous !

Je continue sur ma lancée avec mes problèmes sous Woody.
J'ai installé mplayer (marillat.free.fr), mais impossible de le lancer
autrement que sous root, j'ai le message d'erreur suivant:

$ mplayer 
Using GNU internationalization
Original domain: messages
Original dirname: /usr/share/locale
Current domain: mplayer
Current dirname: /usr/share/locale


MPlayer 0.90pre10-2.95.4 (C) 2000-2002 Arpad Gereoffy (see DOCS)

CPU: Intel Celeron 2/Pentium III Coppermine,Geyserville (Family: 6,
Stepping: 6)
MMX2 supported but disabled
CPUflags:  MMX: 1 MMX2: 0 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 0
Compiled for x86 CPU with extensions: MMX SSE

[cfg] read config file: /home/ajacoutot/.mplayer/gui.conf
vo: X11 running at 1600x1200 with depth 24 and 32 bpp (":0" => local
display)
Reading /home/ajacoutot/.mplayer/codecs.conf: can't open
'/home/ajacoutot/.mplay
er/codecs.conf': No such file or directory
Reading /etc/codecs.conf: 44 audio & 110 video codecs
font: can't open file: /home/ajacoutot/.mplayer/font/font.desc
Font /usr/share/mplayer/font/font.desc loaded successfully! (495 chars)
Failed to open /dev/rtc: Permission denied (mplayer should be setuid
root or /de
v/rtc should be readable by the user.)
Using usleep() timing
Can't open input config file /home/ajacoutot/.mplayer/input.conf : No
such file 
or directory
Input config file /etc/input.conf parsed : 50 binds
Setting up lirc support...
mplayer: could not connect to socket
mplayer: No such file or directory
Failed opening lirc support!
You won't be able to use your remote control


MPlayer interrupted by signal 11 in module: unknown 
- MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with
--enable-d
ebug and make a 'gdb' backtrace and disassembly. For details, see
DOCS/bugreport
s.html section 5.b.
- MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer
code _o
r_ in your drivers _or_ in your gcc version. If you think it's MPlayer's
fault, 
please read DOCS/bugreports.html and follow instructions there. We can't
and won
't help unless you provide these informations when reporting a possible
bug.

Quelqu'un aurait-il une idée ?
Merci d'avance.

Antoine




Reply to: