Feisty package; install fails (/boot/System.map-player)

Bug #84877 reported by Dave Walker
48
Affects Status Importance Assigned to Milestone
vmware-player (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: vmware-player

E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up vmware-player-kernel-modules-2.6.20-8 (2.6.20.2-8.6) ...
FATAL: Could not open '/boot/System.map-player': No such file or directory

FIX: sudo ln -s /boot/System.map-2.6.20-8-generic /boot/System.map-player

Revision history for this message
Terence Simpson (tsimpson) wrote :

I can confirm this bug.
Output from apt-get dist-upgrade:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up vmware-player-kernel-modules-2.6.20-8 (2.6.20.2-8.6) ...
FATAL: Could not open '/boot/System.map-player': No such file or directory
dpkg: error processing vmware-player-kernel-modules-2.6.20-8 (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of vmware-player-kernel-modules:
 vmware-player-kernel-modules depends on vmware-player-kernel-modules-2.6.20-8; however:
  Package vmware-player-kernel-modules-2.6.20-8 is not configured yet.
dpkg: error processing vmware-player-kernel-modules (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 vmware-player-kernel-modules-2.6.20-8
 vmware-player-kernel-modules
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Dave Walker (davewalker) wrote :

found that a dirty "sudo touch /boot/System.map-player" has the same effect.

Revision history for this message
Brandioch.Conner (brandioch-conner) wrote :

I also experience this bug and the
sudo ln -s /boot/System.map-2.6.20-8-generic /boot/System.map-player
fix worked for me.

Revision history for this message
Clifford Gindulis (cliff-gindulis) wrote :

Confirmed, same exact problem and trouble report as Terence above.

The command given by Brandioch above seems to have fixed the problem.

Revision history for this message
jeff419 (adept-marketing-concepts) wrote :

I tried the solution posted and this is what happened:

jeffrey@jeffrey-desktop:~$ sudo ln -s /boot/System.map-2.6.20-8-generic /boot/System.map-player
ln: creating symbolic link `/boot/System.map-player' to `/boot/System.map-2.6.20-8-generic': File exists

After that I tried to upgrade (I already updated before this) and this is what I got.

jeffrey@jeffrey-desktop:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up vmware-player-kernel-modules-2.6.20-8 (2.6.20.2-8.6) ...
FATAL: Could not open '/boot/System.map-player': No such file or directory
dpkg: error processing vmware-player-kernel-modules-2.6.20-8 (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of vmware-player-kernel-modules:
 vmware-player-kernel-modules depends on vmware-player-kernel-modules-2.6.20-8; however:
  Package vmware-player-kernel-modules-2.6.20-8 is not configured yet.
dpkg: error processing vmware-player-kernel-modules (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 vmware-player-kernel-modules-2.6.20-8
 vmware-player-kernel-modules
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm still kind of new to this, but if you need any other info from me let me know and I'll do what I can to help.

Alfredo Matos (alfmatos)
Changed in vmware-player:
status: Unconfirmed → Confirmed
Changed in vmware-player:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.