Error while installing

[AdlerHorst]

Ubuntu 15.10
___________________

Got following Message while installing.

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.

First Installation: checking all kernels...
Building only for 4.2.0-16-generic
Building initial module for 4.2.0-16-generic
Error! Build of vmhgfs.ko failed for: 4.2.0-16-generic (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/9.10.2/build/ for more information.

Mounting shared Folder not working.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pieter Ennes (skion)]

Apparently you need >10.0.0 of open-vm-tools on kernels >4.0 (vmware-tools installer gave that hint)

I tried backporting that from Xenial, by adding Xenial as a source repo in /etc/apt/sources.list, and then build it from the source package:

    cd /tmp
    apt-get update
    apt-get build-dep open-vm-tools open-vm-tools-desktop
    apt-get -b source open-vm-tools open-vm-tools-desktop

    dpkg -i *.deb

But that didn't work either, same error.

Installing from the VMWare Tools CD image did work fine and enabled file sharing with the host system after a reboot.

[Tong Sun (suntong001)]

Same problem for Ubuntu 16.04 LTS Xenial:

apt-get -f install open-vm-tools-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  xdg-utils
Recommended packages:
  open-vm-tools-dkms xserver-xorg-video-vmware
The following NEW packages will be installed:
  open-vm-tools-desktop
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/146 kB of archives.
After this operation, 681 kB of additional disk space will be used.
Selecting previously unselected package open-vm-tools-desktop.
(Reading database ... 69251 files and directories currently installed.)
Preparing to unpack .../open-vm-tools-desktop_2%3a10.0.7-3227872-2ubuntu1_amd64.deb ...
Unpacking open-vm-tools-desktop (2:10.0.7-3227872-2ubuntu1) ...
Setting up open-vm-tools-desktop (2:10.0.7-3227872-2ubuntu1) ...
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.

so mounting shared Folder not working either.

[Tong Sun (suntong001)]

FYI, manual mounting works for Ubuntu 16.04 LTS Xenial, Ref
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1500581

[Tong Sun (suntong001)]

manual mounting works for Ubuntu 16.04 LTS Xenial, Ref
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1551558

[Adrian Pavelescu (virtualadrian)]

Looking at the open-vm-tools package libfuse-dev is a dependency :

-- https://packages.debian.org/source/sid/open-vm-tools

I figured that probably did not get pulled in correctly so I grabbed libfuse-dev on Linux Mint 18

-- sudo apt-get install libfuse-dev

Then I just reconfigured and restarted the VM. Copy/Paste and Monitor Res are back. Here are the specifics of the kernel:

uname -a

4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[Ray Satiro (raysatiro)]

I also had shared folders fail to work after I upgraded from Ubuntu 14.04 to 16.04 LTS and installed the tools. I'm not sure if it's related to this. The error I got was "Failed to get unit file state for run-vmblockx2dfuse.mount: No such file or directory"

When I went to install VMware Tools from the ISO it suggested I use open-vm-tools. I installed that and open-vm-tools-desktop but hgfs didn't work. I read in this bug a comment by virtualadrian to install libfuse-dev so I did that, and then I reinstalled vmtools:

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

I still got the fuse error message after doing that, but I added the line to fstab provided by drolevar in bug 1551558 and rebooted, and now it works.

echo '.host:/ /mnt/hgfs fuse.vmhgfs-fuse allow_other,uid=1000,gid=1000,auto_unmount,users,defaults 0 0' \
 | tee -a /etc/fstab

[Socket (nick-regist)]

Same problem here on Ubuntu 16.04.1 LTS

However this post may point into the right direction: http://osdir.com/ml/ubuntu-bugs/2016-11/msg02399.html

Probably the string "run-vmblock\x2dfuse.mount" is just a typo of the string "run-vmblock-fuse.mount" because \x2d is the hexadecimal escape sequence for the dash character. Probably the deb package needs to be corrected accordingly.

[KennyN (neogeek83)]

Still an issue with:
uname -a
Linux ubunt16 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
apt list open-vm-tools-desktop
Listing... Done
open-vm-tools-desktop/xenial,now 2:10.0.7-3227872-2ubuntu1 amd64 [installed]

But raysatiro's work around did work for me.

[林博仁(Buo-ren, Lin) (buo-ren-lin)]

# Moving my comments from Bug #1639222

The following error messages appear during postinst of open-vm-tools-desktop in Ubuntu 16.10:

```
Created symlink /etc/systemd/system/multi-user.target.wants/run-vmblock\x2dfuse.mount → /lib/systemd/system/run-vmblock\x2dfuse.mount.
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.
```

According to the postinst script:

```
# Automatically added by dh_systemd_enable
# This will only remove masks created by d-s-h on package removal.
deb-systemd-helper unmask run-vmblock\\x2dfuse.mount >/dev/null || true

# was-enabled defaults to true, so new installations run enable.
if deb-systemd-helper --quiet was-enabled run-vmblock\\x2dfuse.mount; then
        # Enables the unit on first installation, creates new
        # symlinks on upgrades if the unit file has changed.
        deb-systemd-helper enable run-vmblock\\x2dfuse.mount >/dev/null || true
else
        # Update the statefile to add new symlinks (if any), which need to be
        # cleaned up on purge. Also remove old symlinks.
        deb-systemd-helper update-state run-vmblock\\x2dfuse.mount >/dev/null || true
fi
```

It seems that the deb-systemd-helper script unable to properly process filepaths containing a slash. View the problem in a different angle it is suspicious for /etc/systemd/system/multi-user.target.wants/run-vmblock\x2dfuse.mount file to have a slash in a filename in the first place, which looks like a escape character for hyphen-minus(0x2d), isn't the file should be named run-vmblock-fuse.mount instead?

[Sankar Tanguturi (sankaraditya)]

I got the same error while installing 'open-vm-tools-desktop' package. Any update for the fix?

Thanks
Sankar.

[vmware-gos-Yuhua (yhzou)]

I get this error in ubuntu 17.10. No update for a long time. Would someone please take care of this issue ?

[Christian Ehrhardt  (paelzer)]

Hi,
the package in 17.10 is at the latest that is in Debian.
Updating to a newer version would break the Feature Freeze and need an exception.
Both Distros have the issue but the error is also non Fatal and it just seems to me that no one had too much issues with it as it is community maintained.

I quickly looked at the case and agree to the check that was done in comment #11.
The easiest fix is likely to rename the file, but a Delta for that in Ubuntu makes the follow on transitions very hard if Debian decides for a different naming.

I'd say lets report this to Debian and pick up on next merge.
I checked and there is no bug for it yet in Debian.
I submitted one and will add it here ocne I get a bug#.

[vmware-gos-Yuhua (yhzou)]

Hi paelzer,
   thanks for your response and actions.

[Christian Ehrhardt  (paelzer)]

yw, yet Debian bug tracker didn't give me a bug number yet (for this and other reports - I assume it is down or on maintenance).
So I beg your pardon this needs some more time than usual.

[vmware-gos-Yuhua (yhzou)]

Hi paelzer,
   thanks for your quick response. Please update this PR when you get feedback from Debian.

   Many thanks for your help!

[Christian Ehrhardt  (paelzer)]

Once linked here the Updates from Debian are automated as seen in c#17 - benefits of Launchpad :-)
That said it is a pure bugfix release and might even now be synced.
I need to check that the other fix around an FTBFS is not breaking for us.
If it works we can sync this latest version even into Artful still.

Building in an artful ppa now to be sure ...

[Christian Ehrhardt  (paelzer)]

Yep also removed the FTBFS that it would get.
So syncing for the fix now - hopefully it builds right as it did in the test ppa then we are good soon.

[Christian Ehrhardt  (paelzer)]

This bug was fixed in the package open-vm-tools - 2:10.1.10-3

---------------
open-vm-tools (2:10.1.10-3) unstable; urgency=medium

  * [00bc9bb] Build with CXXFLAGS=-std=c++14.
    Thanks to Rene Engelhard and Oliver Kurth (Closes: #876121)
  * [6b61376] Re-add .travis.yml.
    Seems it went missing with the last merge.
  * [bf07ae8] Work around dh_systemd escaping bugs again.
    Seems the unit escaping changed with a new dh version.
    Work around the known and reported fails again.
    Thanks to Christian Ehrhardt (Closes: #875657)

 -- Bernd Zeimetz <email address hidden> Thu, 21 Sep 2017 13:24:08 +0200

[Christian Ehrhardt  (paelzer)]

Nice and smooth, I hope that helps you.
Nice weekend!

[vmware-gos-Yuhua (yhzou)]

verified.

It has been fixed when check ubuntu17.10-beta2-desktop64.

thanks all for your effort.

[Markus (markusd1984)]

Is there a way to fix this for the older version? I got the same below:

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.

https://answers.launchpad.net/ubuntu/+source/open-vm-tools/+question/665344

[Christian Ehrhardt  (paelzer)]

We are in the process of making a much newer fixed version available.
There is a long chain of getting buy in and verification from the right party, but the current TL;DR is that in some time there should be a much newer and better open-vm-tools be made available.

Just for the complexity of it I have to beg you for some time.