package configuration failure leads to reconfiguring every time a package gets installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vmware-player (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When installing the vmware player package the one of the modprobe calls that get run /etc/init.
Now whenever I install/upgrade any package(s) it tries to configure the vmware-player package again, and fails because some step in the configuration doesn't like letting run again (which means it will do it again on the next package install).
Output when attempting to configure package:
Now configuring VMware Player. (This may take some time...)
Configuring a bridged network for vmnet0.
Configuring a NAT network for vmnet8.
Probing for an unused private subnet (this can take some time)...
The subnet 172.16.
The file /etc/vmware/
install already exists. Overwrite? [yes]
The file /etc/vmware/
install already exists. Overwrite? [yes]
The file /etc/vmware/
install already exists. Overwrite? [yes]
The file /etc/vmware/
already exists. Overwrite? [yes]
Configuring a host-only network for vmnet1.
Probing for an unused private subnet (this can take some time)...
The subnet 192.168.
The file /etc/vmware/
install already exists. Overwrite? [yes]
The file /etc/vmware/
install already exists. Overwrite? [yes]
The file /etc/vmware/
install already exists. Overwrite? [yes]
Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 failed
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 failed
invoke-rc.d: initscript vmware-player, action "start" failed.
dpkg: error processing vmware-player (--configure):
subprocess post-installation script returned error exit status 1
Yeah, this is very annoying when trying to fix vmware player especially as all the probing ties up the package manager for ages.