> #ChristianEhrhardt (paelzer) wrote on 2018-04-04:
> I'd really need to know if Bionic is affected as well, but can't test it myself.
The ubuntu 18.04 with default open-vm-tools 2:10.2.0-3ubuntu2 also have this issue.
Commenting out the option PrivateTmp=yes in /lib/systemd/system/open-vm-tools.service can fix the issue.
> #David Britton (davidpbritton) wrote on 2018-04-10:
> Could one of you please test that Bionic (18.04) works with the PPA that Christian attached?
Adding ppa with command "sudo add-apt-repository ppa:ci-train-ppa-service/3226" is blocked:
E: The repository 'https://launchpad.net/ci-train-ppa-service/3226 bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
> #ChristianEhrhardt (paelzer) wrote on 2018-04-04:
> I'd really need to know if Bionic is affected as well, but can't test it myself.
The ubuntu 18.04 with default open-vm-tools 2:10.2.0-3ubuntu2 also have this issue. system/ open-vm- tools.service can fix the issue.
Commenting out the option PrivateTmp=yes in /lib/systemd/
> #David Britton (davidpbritton) wrote on 2018-04-10:
> Could one of you please test that Bionic (18.04) works with the PPA that Christian attached?
Adding ppa with command "sudo add-apt-repository ppa:ci- train-ppa- service/ 3226" is blocked:
E: The repository 'https:/ /launchpad. net/ci- train-ppa- service/ 3226 bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.