Comment 8 for bug 57957

Revision history for this message
Jonathan Gordon (launchpad-net-kinobe) wrote :

Well, the only way I was able to find resolution on this problem was to do the following:

1. Found the script that was throwing the errors. In my case it was:
/usr/lib/vmware-player/net-services.sh

2. Backed up the file and then commented out the parts that were causing the problems. In my case it was the following lines:

-- snip --
# Commented out by jmg on 10/6/06 to get vmplayer out of half-installed state
# vmware_exec 'Bridged networking on /dev/vmnet'"$vHubNr" \
# vmware_start_bridge "$vHubNr" "$interface"
               exitcode=$(($exitcode + $?))
            elif [ -n "$hostaddr" -a -n "$netmask" ]; then
               vmware_create_vmnet "$vHubNr"
               vmware_bg_exec 'Host-only networking on /dev/vmnet'"$vHubNr" \
                  vmware_start_hostonly "$vHubNr" 'vmnet'"$vHubNr" \
                  "$hostaddr" "$netmask" 'yes'
               exitcode=$(($exitcode + $?))

               eval 'nat="$vmdb_answer_VNET_'"$vHubNr"'_NAT"'
               if [ "$nat" = 'yes' ]; then
# Commented out by jmg on 10/6/06 to get vmplayer out of half-installed state
# vmware_exec 'NAT service on /dev/vmnet'"$vHubNr" \
# vmware_start_nat "$vHubNr"
                  exitcode=$(($exitcode + $?))
-- snip --

3. Ran the following command:
dpkg --configure -a

The script ran clean and the package was now listed as cleanly installed.

4. Backed up the edited file and clobbered with the original.

Everything's working hunky dory now!

Jonathan.