Bug#758543: same problem

[Daniel Pocock]

I just did a dist-ugprade from wheezy to jessie last week and I have
this same error message.


$ mplayer *.flac
mplayer: error while loading shared libraries: libdvdnavmini.so.4:
cannot open shared object file: No such file or directory



Here is what I have on my system after running apt-get dist-upgrade:


$ dpkg -l | egrep 'libdvdnav|mplayer'
ii  libdvdnav4:amd64    5.0.1-1      amd64        DVD navigation library
ii  mplayer             3:1.1-dmo9   amd64        Ultimate Movie Player
For Linux.



packages.debian.org tells me mplayer is now a virtual package provided
by the mplayer2 package.
   https://packages.debian.org/jessie/mplayer

It seems that what I should have is the mplayer2 package but it wasn't
installed during my dist-upgrade



I was able to manually get it changed to the mplayer2 package and now it
works:

# apt-get install mplayer2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  mplayer
The following NEW packages will be installed:
  mplayer2
0 upgraded, 1 newly installed, 1 to remove and 71 not upgraded.
Need to get 952 kB of archives.
After this operation, 12.7 MB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://mirror.switch.ch/ftp/mirror/debian/ jessie/main mplayer2
amd64 2.0-728-g2c378c7-4+b1 [952 kB]
Fetched 952 kB in 0s (1,720 kB/s)
(Reading database ... 406889 files and directories currently installed.)
Removing mplayer (3:1.1-dmo9) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.7.0.2-5) ...
Selecting previously unselected package mplayer2.
(Reading database ... 406871 files and directories currently installed.)
Preparing to unpack .../mplayer2_2.0-728-g2c378c7-4+b1_amd64.deb ...
Unpacking mplayer2 (2.0-728-g2c378c7-4+b1) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up mplayer2 (2.0-728-g2c378c7-4+b1) ...


Is there some other bug for this issue now or should this bug be re-opened?