Bug #1771750 “package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 f...” : Bugs : open-vm-tools package : Ubuntu

Revision history for this message

jwvdleest (j-w-vanderleest) wrote on 2018-05-17:

#1

AptOrdering.txt Edit (396 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (801 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (190.2 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (6.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1003 bytes, text/plain; charset="utf-8")
modified.conffile..etc.pam.d.vmtoolsd.txt Edit (400 bytes, text/plain; charset="utf-8")
modified.conffile..etc.vmware-tools.poweroff-vm-default.txt Edit (718 bytes, text/plain; charset="utf-8")
modified.conffile..etc.vmware-tools.poweron-vm-default.txt Edit (718 bytes, text/plain; charset="utf-8")
modified.conffile..etc.vmware-tools.resume-vm-default.txt Edit (3.2 KiB, text/plain; charset="utf-8")
modified.conffile..etc.vmware-tools.suspend-vm-default.txt Edit (2.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2018-05-17:

#2

Hi jwvdleest,
the update is a normal package update - nothing super-special.
But from your logs I see an issue on your system.

On 2018-05-17 07:00:08 there was a full "apt-get dist-upgrade -y".
This is what - among other updates - pulled in the newer open-vm-tools.

But this not only asked you for modifications of conffiles which are:
a) meant to be auto-generated
b) if changed it will ask you on updates if you want/need to keep your content

To be sure I tried a base Xenial install with these files unchanged - it upgrades without asking me to the new version of open-vm-tools.

Your system lists these files as modified on: 2017-03-10T09:27
Maybe that helps to find what/why they were changed in the first place.

With those files modified DPDK has no choice (unless you force it with e.g. --force-confnew see man dpkg) but to ask you about how to handle it.

Even worse, if this would not have stopped there you'd still have a failed update.
Your system lists also plenty of files deleted
modified.conffile..etc.vmware-tools.vgauth.conf: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-hasFacetAndProperty.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-instance.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.dtd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.catalog.xml: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.datatypes.dtd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.saml-schema-assertion-2.0.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xenc-schema.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xml.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xmldsig-core-schema.xsd: [deleted]

This would have broken a restart of the associated services which has to happen on an upgrade.
So chances are high this would have hit you right after.
If you don't want open-vm-tools you can just remove it fully through "apt remove --purge".
If you need it then I'd ask you to configure it so that it can work, only then it can properly upgrade.

Hi jwvdleest,
the update is a normal package update - nothing super-special.
But from your logs I see an issue on your system.

On 2018-05-17  07:00:08 there was a full "apt-get dist-upgrade -y".
This is what - among other updates - pulled in the newer open-vm-tools.

But this not only asked you for modifications of conffiles which are:
a) meant to be auto-generated
b) if changed it will ask you on updates if you want/need to keep your content

To be sure I tried a base Xenial install with these files unchanged - it upgrades without asking me to the new version of open-vm-tools.

Your system lists these files as modified on: 2017-03-10T09:27
Maybe that helps to find what/why they were changed in the first place.

With those files modified DPDK has no choice (unless you force it with e.g. --force-confnew see man dpkg) but to ask you about how to handle it.

Even worse, if this would not have stopped there you'd still have a failed update.
Your system lists also plenty of files deleted
modified.conffile..etc.vmware-tools.vgauth.conf: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-hasFacetAndProperty.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-instance.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.dtd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.catalog.xml: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.datatypes.dtd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.saml-schema-assertion-2.0.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xenc-schema.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xml.xsd: [deleted]
modified.conffile..etc.vmware-tools.vgauth.schemas.xmldsig-core-schema.xsd: [deleted]

This would have broken a restart of the associated services which has to happen on an upgrade.
So chances are high this would have hit you right after.
If you don't want open-vm-tools you can just remove it fully through "apt remove --purge".
If you need it then I'd ask you to configure it so that it can work, only then it can properly upgrade.

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2018-05-17:

#3

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in open-vm-tools (Ubuntu):
status:	New → Incomplete

Revision history for this message

jwvdleest (j-w-vanderleest) wrote on 2018-05-17: Re: [Bug 1771750] Re: package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to install/upgrade: bestandseinde op stdin bij de prompt i.v.m. configuratiebestand

#4

Download full text (4.8 KiB)

Dear Christian,

Thanks for your extensive replay.
Ik Willem remove VMware tools, I don't need them anymore.

Met vriendelijke groeten,

Jan Willem van der Leest
Nirrewortel 13
3453 VP De Meern
T: 030-6080646
M: 06-15313888

Op do 17 mei 2018 12:10 schreef  Christian Ehrhardt  <
<email address hidden>>:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> On upgrading a service this service has to be restarted to pick up the
> fixes.
> Rather rarely a real issue occurs that the newer version does e.g. fail
> with the formerly working configuration.
> But most of the time what happens is, that a service was installed, but
> stays unconfigured or experimented with but left in a broken state.
>
> Now on any update of the related packages that service has to be
> restarted, but since its config is incomplete/faulty it fails to restart.
> Therefore the update of that package has to consider itself incomplete.
>
> Depending on your particular case there are two solutions:
> - either remove the offending package if you don't want to continue using
> it.
> - Or if you do want to keep it please fix the configuration so that
> re-starting the service will work.
>
> Since it seems likely to me that this is a local configuration problem,
> rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
>
> If indeed this is a local configuration problem, you can find pointers
> to get help for this sort of problem here:
> http://www.ubuntu.com/support/community
>
> Or if you believe that this is really a bug, then you may find it
> helpful to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem,
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your system, and then change the bug status back to New.
>
> ** Changed in: open-vm-tools (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771750
>
> Title:
> package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to
> install/upgrade: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
>
> Status in open-vm-tools package in Ubuntu:
> Incomplete
>
> Bug description:
> Could be caused as a background process? Or while having an update?
> Update management is active while causing the bug.
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1
> ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
> Uname: Linux 4.4.0-124-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.17
> Architecture: amd64
> Date: Thu May 17 07:00:56 2018
> ErrorMessage: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
> InstallationDate: Installed on 2016-11-29 (533 days ago)
> InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release
> amd64 (20160719)
> RelatedPackageVersions:
> dpkg 1.18.4ubuntu1.4
> apt 1.2.26
> SourcePackage: open-vm-tools
> Title: package open-vm-t...

Dear Christian,

Thanks for your extensive replay.
Ik Willem remove VMware tools, I don't need them anymore.

Met vriendelijke groeten,

Jan Willem van der Leest
Nirrewortel 13
3453 VP De Meern
T: 030-6080646
M: 06-15313888

Op do 17 mei 2018 12:10 schreef  Christian Ehrhardt  <
1771750@bugs.launchpad.net>:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> On upgrading a service this service has to be restarted to pick up the
> fixes.
> Rather rarely a real issue occurs that the newer version does e.g. fail
> with the formerly working configuration.
> But most of the time what happens is, that a service was installed, but
> stays unconfigured or experimented with but left in a broken state.
>
> Now on any update of the related packages that service has to be
> restarted, but since its config is incomplete/faulty it fails to restart.
> Therefore the update of that package has to consider itself incomplete.
>
> Depending on your particular case there are two solutions:
> - either remove the offending package if you don't want to continue using
> it.
> - Or if you do want to keep it please fix the configuration so that
> re-starting the service will work.
>
> Since it seems likely to me that this is a local configuration problem,
> rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
>
> If indeed this is a local configuration problem, you can find pointers
> to get help for this sort of problem here:
> http://www.ubuntu.com/support/community
>
> Or if you believe that this is really a bug, then you may find it
> helpful to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem,
> explain why you believe this is a bug in Ubuntu rather than a problem
> specific to your system, and then change the bug status back to New.
>
> ** Changed in: open-vm-tools (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771750
>
> Title:
>   package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to
>   install/upgrade: bestandseinde op stdin bij de prompt i.v.m.
>   configuratiebestand
>
> Status in open-vm-tools package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Could be caused as a background process? Or while having an update?
>   Update management is active while causing the bug.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1
>   ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
>   Uname: Linux 4.4.0-124-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.17
>   Architecture: amd64
>   Date: Thu May 17 07:00:56 2018
>   ErrorMessage: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
>   InstallationDate: Installed on 2016-11-29 (533 days ago)
>   InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release
> amd64 (20160719)
>   RelatedPackageVersions:
>    dpkg 1.18.4ubuntu1.4
>    apt  1.2.26
>   SourcePackage: open-vm-tools
>   Title: package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to
> install/upgrade: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   modified.conffile..etc.vmware-tools.vgauth.conf: [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-hasFacetAndProperty.xsd:
> [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-instance.xsd:
> [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.dtd:
> [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.xsd:
> [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.catalog.xml: [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.datatypes.dtd:
> [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.saml-schema-assertion-2.0.xsd:
> [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.xenc-schema.xsd:
> [deleted]
>   modified.conffile..etc.vmware-tools.vgauth.schemas.xml.xsd: [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.xmldsig-core-schema.xsd:
> [deleted]
>   mtime.conffile..etc.pam.d.vmtoolsd: 2017-03-10T09:27:54.376885
>   mtime.conffile..etc.vmware-tools.poweroff-vm-default:
> 2017-03-10T09:27:44.108950
>   mtime.conffile..etc.vmware-tools.poweron-vm-default:
> 2017-03-10T09:27:40.180974
>   mtime.conffile..etc.vmware-tools.resume-vm-default:
> 2017-03-10T09:27:43.680952
>   mtime.conffile..etc.vmware-tools.suspend-vm-default:
> 2017-03-10T09:27:43.204955
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1771750/+subscriptions
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-07-17:

#5

[Expired for open-vm-tools (Ubuntu) because there has been no activity for 60 days.]

Changed in open-vm-tools (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

jwvdleest (j-w-vanderleest) wrote on 2018-07-17:

#6

Download full text (3.2 KiB)

Thanks!

Met vriendelijke groeten,

Jan Willem van der Leest
Nirrewortel 13
3453 VP De Meern
T: 030-6080646
M: 06-15313888

Op di 17 jul. 2018 06:25 schreef Launchpad Bug Tracker <
<email address hidden>>:

> [Expired for open-vm-tools (Ubuntu) because there has been no activity
> for 60 days.]
>
> ** Changed in: open-vm-tools (Ubuntu)
> Status: Incomplete => Expired
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771750
>
> Title:
> package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to
> install/upgrade: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
>
> Status in open-vm-tools package in Ubuntu:
> Expired
>
> Bug description:
> Could be caused as a background process? Or while having an update?
> Update management is active while causing the bug.
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1
> ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
> Uname: Linux 4.4.0-124-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.17
> Architecture: amd64
> Date: Thu May 17 07:00:56 2018
> ErrorMessage: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
> InstallationDate: Installed on 2016-11-29 (533 days ago)
> InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release
> amd64 (20160719)
> RelatedPackageVersions:
> dpkg 1.18.4ubuntu1.4
> apt 1.2.26
> SourcePackage: open-vm-tools
> Title: package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to
> install/upgrade: bestandseinde op stdin bij de prompt i.v.m.
> configuratiebestand
> UpgradeStatus: No upgrade log present (probably fresh install)
> modified.conffile..etc.vmware-tools.vgauth.conf: [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-hasFacetAndProperty.xsd:
> [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema-instance.xsd:
> [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.dtd:
> [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.XMLSchema.xsd:
> [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.catalog.xml: [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.datatypes.dtd:
> [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.saml-schema-assertion-2.0.xsd:
> [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.xenc-schema.xsd:
> [deleted]
> modified.conffile..etc.vmware-tools.vgauth.schemas.xml.xsd: [deleted]
>
> modified.conffile..etc.vmware-tools.vgauth.schemas.xmldsig-core-schema.xsd:
> [deleted]
> mtime.conffile..etc.pam.d.vmtoolsd: 2017-03-10T09:27:54.376885
> mtime.conffile..etc.vmware-tools.poweroff-vm-default:
> 2017-03-10T09:27:44.108950
> mtime.conffile..etc.vmware-tools.poweron-vm-default:
> 2017-03-10T09:27:40.180974
> mtime.conffile..etc.vmware-tools.resume-vm-default:
> 2017-03-10T09:27:43.680952
> mtime.conffile..etc.vmware-tools.suspend-vm-default:
> 2017-03-10T09:27:43.204955
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/o...

Ubuntu
open-vm-tools package

package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to install/upgrade: bestandseinde op stdin bij de prompt i.v.m. configuratiebestand

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuopen-vm-tools package

package open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 failed to install/upgrade: bestandseinde op stdin bij de prompt i.v.m. configuratiebestand

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
open-vm-tools package