open-vm-tools-desktop Installed: 2:10.0.7-3227872-5ubuntu1~16.04.1 version difference?

Asked by Markus on 2018-03-07

I had Open-vm-tools and open-vm-tools-desktop working fine on ubuntu 16.04 for a while but recently when trying to install new packages i get the below error re version difference:

The following packages have unmet dependencies:
 open-vm-tools-desktop : Depends: open-vm-tools (= 2:10.0.7-3227872-5ubuntu1~16.04.1) but 2:10.0.7-3227872-5ubuntu1~16.04.2 is to be installed
                         Recommends: xserver-xorg-input-vmmouse but it is not going to be installed

I tried to remove and purge it in order to re-install but had to change the pre-removal script to make that work which was mentioned here
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1751016

I don't understand why this version discrepancy appeared and wondering if there is any other way to solve this instead of re-installing?

More Details:

apt-cache policy open-vm-tools open-vm-tools-desktop
open-vm-tools:
  Installed: 2:10.0.7-3227872-5ubuntu1~16.04.2
  Candidate: 2:10.0.7-3227872-5ubuntu1~16.04.2
  Version table:
 *** 2:10.0.7-3227872-5ubuntu1~16.04.2 500
        500 http://ie.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2:10.0.7-3227872-2ubuntu1 500
        500 http://ie.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
open-vm-tools-desktop:
  Installed: 2:10.0.7-3227872-5ubuntu1~16.04.1
  Candidate: 2:10.0.7-3227872-5ubuntu1~16.04.2
  Version table:
     2:10.0.7-3227872-5ubuntu1~16.04.2 500
        500 http://ie.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
 *** 2:10.0.7-3227872-5ubuntu1~16.04.1 100
        100 /var/lib/dpkg/status
     2:10.0.7-3227872-2ubuntu1 500
        500 http://ie.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Try:

sudo apt-get install open-vm-tools-desktop open-vm-tools

May work

Markus (markusd1984) said : #2

thanks, I got to the below where it seems to be still an issue with open-vm-tools-desktop due to "Failed to get unit file state for run-vmblockx2dfuse.mount: No such file or directory run-vmblock\x2dfuse.mount is a disabled or a static unit, not starting it."

More Details:
Setting up open-vm-tools (2:10.0.7-3227872-5ubuntu1~16.04.2) ...

Configuration file '/etc/vmware-tools/tools.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : start a shell to examine the situation
 The default action is to keep your current version.
*** tools.conf (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/vmware-tools/tools.conf ...

Setting up open-vm-tools-desktop (2:10.0.7-3227872-5ubuntu1~16.04.2) ...

Failed to get unit file state for run-vmblockx2dfuse.mount: No such file or directory
run-vmblock\x2dfuse.mount is a disabled or a static unit, not starting it.

Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Setting up engrampa (1.12.0-2ubuntu0.1) ...
Setting up caja (1.12.7-1ubuntu0.1) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for initramfs-tools (0.122ubuntu8.10) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-36-generic
Processing triggers for resolvconf (1.78ubuntu6) ...
Processing triggers for libapache2-mod-php5.6 (5.6.33-3+ubuntu16.04.1+deb.sury.org+1) ...

Markus (markusd1984) said : #3

Not sure if this is a big deal and can consider it resolved?
I should clarify that the version has updated now.

open-vm-tools-desktop:
  Installed: 2:10.0.7-3227872-5ubuntu1~16.04.2
  Candidate: 2:10.0.7-3227872-5ubuntu1~16.04.2

Markus (markusd1984) said : #4

I think this is the same as others seem to be affected
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1639222
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1513531

in case the below info helps (shows its loaded/active yet failed unmounting?!??)

nonroot@Server1:~$ sudo systemctl status run-vmblock\\x2dfuse.mount
● run-vmblock\x2dfuse.mount - VMware vmblock fuse mount
   Loaded: loaded (/proc/self/mountinfo; enabled; vendor preset: enabled)
   Active: active (mounted) (Result: exit-code) since Fri 2018-02-23 16:49:25 GMT; 1 weeks 4 days ago
    Where: /run/vmblock-fuse
     What: vmware-vmblock
     Docs: https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/vmblock-fuse/design.txt
   CGroup: /system.slice/run-vmblock\x2dfuse.mount
           └─307 vmware-vmblock-fuse /run/vmblock-fuse -o rw,subtype=vmware-vmblock,default_permissions,allow_other,dev,suid

Feb 23 16:49:25 Server1 umount[15905]: use the device is found by lsof(8) or fuser(1).)
Feb 23 16:49:25 Server1 systemd[1]: run-vmblock\x2dfuse.mount: Mount process exited, code=exited status=32
Feb 23 16:49:25 Server1 systemd[1]: Failed unmounting VMware vmblock fuse mount.
Feb 23 16:49:25 Server1 systemd[1]: Unmounting VMware vmblock fuse mount...
Feb 23 16:49:25 Server1 umount[15908]: umount: /run/vmblock-fuse: target is busy
Feb 23 16:49:25 Server1 umount[15908]: (In some cases useful info about processes that
Feb 23 16:49:25 Server1 umount[15908]: use the device is found by lsof(8) or fuser(1).)
Feb 23 16:49:25 Server1 systemd[1]: run-vmblock\x2dfuse.mount: Mount process exited, code=exited status=32
Feb 23 16:49:25 Server1 systemd[1]: Failed unmounting VMware vmblock fuse mount.
Mar 07 12:43:51 Server1 systemd[1]: Mounted VMware vmblock fuse mount.

If you reboot now is it happier?

Markus (markusd1984) said : #6

Thanks actionparsnip, that solved my question.