Hello Dariusz, or anyone else affected, Accepted open-vm-tools into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/open-vm- tools/2:10.1.10-3ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: open-vm-tools (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful ** Changed in: open-vm-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1748122 Title: 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 Committed Status in open-vm-tools source package in Artful: Fix Committed Bug description: [Impact] * 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 vmtoolsd. 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: https://bugs.launchpad.net/open-vm-tools/+bug/1748122/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : [email protected] Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
