mplayer just breaks

proudclod · 05-25-2004, 05:14 PM

Hi,

Mplayer used to work fine.

Then a yum update broke the Xv mode. No biggie, I used gl2 instead.

Now another yum update, and i get this error when i start mplayer:

Code:

tom@delphinius-ii tom$ mplayer
mplayer: /usr/X11R6/lib/nvidia-graphics-1.0-4496/libXvMCNVIDIA_dynamic.so.1: no version information available (required by mplayer)
MPlayer 1.0pre4-3.3.3 (C) 2000-2004 MPlayer Team

But that file exists as a symlink to the correct file. I even tried putting a copy of the real file there, but i still get an error. Help?

Mega Man X · 05-25-2004, 05:49 PM

What have you been updating? I found very very few reasons to update anything besides security applications... Well, the above problem is complaining against nvidia, so if I was you, I'd either reinstall nvidia drivers, and if that does not work, reinstall mplayer

proudclod · 05-25-2004, 06:39 PM

The point is, I run FC2, a radeon 9600xt and ati's proprietary drivers.

I appear to have 'acquired' the NVidia drivers through yum.

And I just used yum update

proudclod · 05-26-2004, 11:36 AM

This thread seems a good place to ask whether it's bad etiquette here at LQ to bump threads?

Mega Man X · 05-26-2004, 01:12 PM

ghehe, nah, we all do that sometimes

. However, there're some rules that tells you to wait at least 24 hours before use a "bump"

.

How did you install mplayer? apt-get? rpm? source?. I'd recommend you removing mplayer and installing it again with apt-get, so _maybe_, mplayer will use the correct drivers. It worked on Redhat 9.0 so hopefully it will work on Fedora

.

proudclod · 05-27-2004, 01:43 PM

Nope, uninstall then reinstall didn't work. I've heard talk of troubles with Xvideo overlay and the ATI drivers. Could that be part of the problem?

proudclod · 05-28-2004, 02:14 PM

Ok, my problem with the program not running was simply that I hadn't installed mplayer-skins rpm, and so gmplayer had broken.

As for the Xvideo breakage: http://freedesktop.org/pipermail/xor...ay/000449.html

That's the kitten. Closing my web browser, and XMMS, seems to solve the problem for now.