This bug was fixed in the package open-vm-tools -

open-vm-tools (2:10.0.7-3227872-5ubuntu1~16.04.2) xenial; urgency=medium

  * Make tools.conf template useful. (LP: #1748122)

 -- Dariusz Gadomski <>  Thu, 15 Feb 2018
11:19:17 +0100

** Changed in: open-vm-tools (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  incorrect tools.conf template is shipped with Ubuntu

Status in VMWare tools:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Trusty:
  Fix Committed
Status in open-vm-tools source package in Xenial:
  Fix Released
Status in open-vm-tools source package in Artful:
  Fix Released

Bug description:

   * The default tools.conf template shipped with the Ubuntu package is
  useless - it gets cleared on the first run as it contains an
  unrecognized content.

  [Test Case]

   * Install open-vm-tools.
   * Check contents of /etc/vmware-tools/tools.conf.
   * Start vmtoolsd service e.g. by systemctl start open-vm-tools.
   * Check tools.conf contents again.

  Expected result:
  Config is read an left untouched.

  Actual result:
  Config file is cleared.

  [Regression Potential]

   * If any of the parameters in the template is set to a non-default value
  the behaviour of vmtoolsd may change slightly (e.g. different log verbosity, 
log target - file vs. syslog).
     But people will get the usual conffile changed prompts, so those who 
modified it will have to consciously decide which makes it safe.

  [Other Info]

   * Original bug description:

  The tools.conf template shipped with Ubuntu (debian/local/tools.conf)
  is incorrect.

  It's current contents:
  bindir = "/usr/bin"
  do not mean anything to open-vm-tools - it's not interpreted in any way by 

  Moreover, on the first launch this content is cleared by a piece of
  code doing a "config upgrade".

  I believe replacing it with a more meaningful content is necessary.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to