Bug 124036 - mplayer application does not work after upgrading from Fedora Core to Fedora Core 2.
mplayer application does not work after upgrading from Fedora Core to Fedora ...
Product: Fedora
Classification: Fedora
Component: gnome-media (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Colin Walters
Depends On:
  Show dependency treegraph
Reported: 2004-05-22 23:11 EDT by Reginald McCord
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-23 10:40:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Reginald McCord 2004-05-22 23:11:27 EDT
Description of problem:  Mplayer no longer works after upgrading to
Fedira Core 2.  I get the following error if I attempt to start the
application from a command line:

[rmccord@Hendrix rmccord]$ gmplayer
gmplayer: error while loading shared libraries: libdv.so.2: cannot
open shared object file: No such file or directory

After running the 'find' command as root (find / -name gmplayer -print
), its located in '/usr/bin/gmplayer'.  An rpm query shows the
application version: 
[root@Hendrix rmccord]# rpm -q mplayer
However libdv.so.2 was never found.

Version-Release number of selected component (if applicable):

How reproducible:
Run 'Movie Player' from gnome menu, or 'gmplayer' from command line.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Colin Walters 2004-05-23 10:40:31 EDT
We don't support mplayer.
Comment 2 Mark Allen 2004-11-08 22:00:01 EST
You can work around this problem with FC2.  Search in your lib
directory,  mine is /usr/lib  for file name like libdv*.  I found
libdv.so.4.  Then create symbolic link to libdv.so.2:

ln -s libdv.so.4 libdv.so.2

For FC2  libdv.so.4  is linked to file libdv.so.4.0.0

it's all good

Note You need to log in before you can comment on or make changes to this bug.