package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed dms-core package post-installation script subprocess returned error exit status 3

[Donald Wilde]

I have gotten a number of these from 20.04 post-release while I was attempting to re-install packages (that worked in 18.04.4) from a list through a Ruby script.

If I try to manually install any one of the dms* packages it fails. Removing works, but as soon as I re-install it dies again.

I was able to get apport working again by clearing /var/crash. I am going to put a tail on syslog to see it happening live.

This is Bind9, so that is why I am reporting it also to Security team.

I am also getting 'audit' failures that come from AppArmor. I believe these revolve around the snapd subsystem. They occurred in 18.04.4, which was why I was eager to try an update.

Thanks in advance. I'll be glad to try a patch.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: dms-core 1.0.8.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 11:20:51 2020
ErrorMessage: installed dms-core package post-installation script subprocess returned error exit status 3
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2
SourcePackage: dms
Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed dms-core package post-installation script subprocess returned error exit status 3
UpgradeStatus: No upgrade log present (probably fresh install)

[Donald Wilde (dwilde1)]

I already attached the ruby script to the original bug report.

package-list.txt is the original source list, made up manually from a
tool that gave me a dated list of pkg installs to my several-years-old
18.04 system. package-log.txt is simply a pass-fail log. Since dms is
almost certainly being installed as a dependency, the higher-level
package should show up later in the fail list.

On 4/24/20, Donald Wilde <email address hidden> wrote:
> *** This bug is a security vulnerability ***
>
> Private security bug reported:
>
> I have gotten a number of these from 20.04 post-release while I was
> attempting to re-install packages (that worked in 18.04.4) from a list
> through a Ruby script.
>
> If I try to manually install any one of the dms* packages it fails.
> Removing works, but as soon as I re-install it dies again, usually with 'unable to initialize' messages.

I have checked synaptic and it appears that the basic dbus packages
are all there. The daemon is running.

>
> I was able to get apport working again by clearing /var/crash. I am
> going to put a tail on syslog to see it happening live.
>
> This is Bind9, so that is why I am reporting it also to Security team.
>
> I am also getting 'audit' failures that come from AppArmor. I believe
> these revolve around the snapd subsystem. They occurred in 18.04.4,
> which was why I was eager to try an update.
>
> Thanks in advance. I'll be glad to try a patch.
>
> ProblemType: Package
> DistroRelease: Ubuntu 20.04
> Package: dms-core 1.0.8.1-1ubuntu2
> ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
> Uname: Linux 5.4.0-26-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27
> Architecture: amd64
> CasperMD5CheckResult: skip
> Date: Fri Apr 24 11:20:51 2020
> ErrorMessage: installed dms-core package post-installation script subprocess
> returned error exit status 3
> InstallationDate: Installed on 2020-04-24 (0 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
> 3.8.2-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
> 2.7.17-4
> RelatedPackageVersions:
> dpkg 1.19.7ubuntu3
> apt 2.0.2
> SourcePackage: dms
> Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
> installed dms-core package post-installation script subprocess returned
> error exit status 3
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: dms (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 apport-package focal
>
> ** Attachment added: "script used to install packages"
>
> https://bugs.launchpad.net/bugs/1874901/+attachment/5359800/+files/Packages.rb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874901
>
> Title:
> package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
> dms-core package post-installation script subprocess returned error
> exit status 3
>
> Status in dms package in Ubuntu:
> New
>
> Bug description:
> I have gotten a number of these from 20.04 post-release while I was
> attem...

[Donald Wilde (dwilde1)]

Hi, team --

The snapd issue doesn't cause me grief on my working system, but this
does. I'm going to have to revert to 18.04.4 soon in order to keep my
regular work going.

I'll keep this up for now, but I can't even install KVM without the
dms-core crashing the package install, so I am challenged to stay put
for long. Figure that Monday I'll re-install 18.04.

I see that several others are seeingh the same situation, so I hope
you have enough input to be able to squish this buggly critter! :D

On 4/24/20, Donald Wilde <email address hidden> wrote:
> I already attached the ruby script to the original bug report.
>
> package-list.txt is the original source list, made up manually from a
> tool that gave me a dated list of pkg installs to my several-years-old
> 18.04 system. package-log.txt is simply a pass-fail log. Since dms is
> almost certainly being installed as a dependency, the higher-level
> package should show up later in the fail list.
>
> On 4/24/20, Donald Wilde <email address hidden> wrote:
>> *** This bug is a security vulnerability ***
>>
>> Private security bug reported:
>>
>> I have gotten a number of these from 20.04 post-release while I was
>> attempting to re-install packages (that worked in 18.04.4) from a list
>> through a Ruby script.
>>
>> If I try to manually install any one of the dms* packages it fails.
>> Removing works, but as soon as I re-install it dies again, usually with
>> 'unable to initialize' messages.
>
> I have checked synaptic and it appears that the basic dbus packages
> are all there. The daemon is running.
>
>>
>> I was able to get apport working again by clearing /var/crash. I am
>> going to put a tail on syslog to see it happening live.
>>
>> This is Bind9, so that is why I am reporting it also to Security team.
>>
>> I am also getting 'audit' failures that come from AppArmor. I believe
>> these revolve around the snapd subsystem. They occurred in 18.04.4,
>> which was why I was eager to try an update.
>>
>> Thanks in advance. I'll be glad to try a patch.
>>
>> ProblemType: Package
>> DistroRelease: Ubuntu 20.04
>> Package: dms-core 1.0.8.1-1ubuntu2
>> ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>> Uname: Linux 5.4.0-26-generic x86_64
>> ApportVersion: 2.20.11-0ubuntu27
>> Architecture: amd64
>> CasperMD5CheckResult: skip
>> Date: Fri Apr 24 11:20:51 2020
>> ErrorMessage: installed dms-core package post-installation script
>> subprocess
>> returned error exit status 3
>> InstallationDate: Installed on 2020-04-24 (0 days ago)
>> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>> Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
>> 3.8.2-0ubuntu2
>> PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
>> 2.7.17-4
>> RelatedPackageVersions:
>> dpkg 1.19.7ubuntu3
>> apt 2.0.2
>> SourcePackage: dms
>> Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
>> installed dms-core package post-installation script subprocess returned
>> error exit status 3
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> ** Affects: dms (Ubuntu)
>> Importance: Undecided
>> Status: New
>>
>>
>>...

[Seth Arnold (seth-arnold)]

Hello Donald, is the .docx attachment on this bug report intentional? I wanted to set this bug to public visibility so others could see it, but if this file was not intentionally attached, perhaps you'd rather delete the attachment before making the bug publicly visible.

For the snapd issue, it'd be worth opening a bug report with the snap team, or perhaps a thread on https://forum.snapcraft.io/

Thanks

[Donald Wilde (dwilde1)]

On 4/27/20, Seth Arnold <email address hidden> wrote:
> Hello Donald, is the .docx attachment on this bug report intentional? I
> wanted to set this bug to public visibility so others could see it, but
> if this file was not intentionally attached, perhaps you'd rather delete
> the attachment before making the bug publicly visible.
>
> For the snapd issue, it'd be worth opening a bug report with the snap
> team, or perhaps a thread on https://forum.snapcraft.io/
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874901
>
> Title:
> package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
> dms-core package post-installation script subprocess returned error
> exit status 3
>
> Status in dms package in Ubuntu:
> New
>
> Bug description:
> I have gotten a number of these from 20.04 post-release while I was
> attempting to re-install packages (that worked in 18.04.4) from a list
> through a Ruby script.
>
> If I try to manually install any one of the dms* packages it fails.
> Removing works, but as soon as I re-install it dies again.
>
> I was able to get apport working again by clearing /var/crash. I am
> going to put a tail on syslog to see it happening live.
>
> This is Bind9, so that is why I am reporting it also to Security team.
>
> I am also getting 'audit' failures that come from AppArmor. I believe
> these revolve around the snapd subsystem. They occurred in 18.04.4,
> which was why I was eager to try an update.
>
> Thanks in advance. I'll be glad to try a patch.
>
> ProblemType: Package
> DistroRelease: Ubuntu 20.04
> Package: dms-core 1.0.8.1-1ubuntu2
> ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
> Uname: Linux 5.4.0-26-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27
> Architecture: amd64
> CasperMD5CheckResult: skip
> Date: Fri Apr 24 11:20:51 2020
> ErrorMessage: installed dms-core package post-installation script
> subprocess returned error exit status 3
> InstallationDate: Installed on 2020-04-24 (0 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
> 3.8.2-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
> 2.7.17-4
> RelatedPackageVersions:
> dpkg 1.19.7ubuntu3
> apt 2.0.2
> SourcePackage: dms
> Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
> installed dms-core package post-installation script subprocess returned
> error exit status 3
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+subscriptions
>

I already attached the ruby script to the original bug report.

package-list.txt is the original source list, made up manually from a
tool that gave me a dated list of pkg installs to my several-years-old
18.04 system. package-log.txt is simply a pass-fail log. Since dms is
almost certainly being installed as a dependency, the higher-level
package should s...

[Donald Wilde (dwilde1)]

You are right, Seth, that was dumb. Thanks!

On 4/27/20, Donald Wilde <email address hidden> wrote:
> On 4/27/20, Seth Arnold <email address hidden> wrote:
>> Hello Donald, is the .docx attachment on this bug report intentional? I
>> wanted to set this bug to public visibility so others could see it, but
>> if this file was not intentionally attached, perhaps you'd rather delete
>> the attachment before making the bug publicly visible.
>>
>> For the snapd issue, it'd be worth opening a bug report with the snap
>> team, or perhaps a thread on https://forum.snapcraft.io/
>>
>> Thanks
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1874901
>>
>> Title:
>> package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
>> dms-core package post-installation script subprocess returned error
>> exit status 3
>>
>> Status in dms package in Ubuntu:
>> New
>>
>> Bug description:
>> I have gotten a number of these from 20.04 post-release while I was
>> attempting to re-install packages (that worked in 18.04.4) from a list
>> through a Ruby script.
>>
>> If I try to manually install any one of the dms* packages it fails.
>> Removing works, but as soon as I re-install it dies again.
>>
>> I was able to get apport working again by clearing /var/crash. I am
>> going to put a tail on syslog to see it happening live.
>>
>> This is Bind9, so that is why I am reporting it also to Security team.
>>
>> I am also getting 'audit' failures that come from AppArmor. I believe
>> these revolve around the snapd subsystem. They occurred in 18.04.4,
>> which was why I was eager to try an update.
>>
>> Thanks in advance. I'll be glad to try a patch.
>>
>> ProblemType: Package
>> DistroRelease: Ubuntu 20.04
>> Package: dms-core 1.0.8.1-1ubuntu2
>> ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>> Uname: Linux 5.4.0-26-generic x86_64
>> ApportVersion: 2.20.11-0ubuntu27
>> Architecture: amd64
>> CasperMD5CheckResult: skip
>> Date: Fri Apr 24 11:20:51 2020
>> ErrorMessage: installed dms-core package post-installation script
>> subprocess returned error exit status 3
>> InstallationDate: Installed on 2020-04-24 (0 days ago)
>> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>> Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
>> 3.8.2-0ubuntu2
>> PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
>> 2.7.17-4
>> RelatedPackageVersions:
>> dpkg 1.19.7ubuntu3
>> apt 2.0.2
>> SourcePackage: dms
>> Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
>> installed dms-core package post-installation script subprocess returned
>> error exit status 3
>> UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+subscriptions
>>
>
> I already attached the ruby script to the original bug report.
>
> package-list.txt is the original source list, made up manually from a
> tool that gave me a dated list of pkg install...

[Eduardo Barretto (ebarretto)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Donald Wilde (dwilde1)]

Understood. Better to be safe than sorry. Thanks, Eduardo.

On 4/29/20, Eduardo Barretto <email address hidden> wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug. I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Attachment removed: "Resume_DSW_2020-April.docx"
>
> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+attachment/5359825/+files/Resume_DSW_2020-April.docx
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1874901
>
> Title:
> package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade: installed
> dms-core package post-installation script subprocess returned error
> exit status 3
>
> Status in dms package in Ubuntu:
> New
>
> Bug description:
> I have gotten a number of these from 20.04 post-release while I was
> attempting to re-install packages (that worked in 18.04.4) from a list
> through a Ruby script.
>
> If I try to manually install any one of the dms* packages it fails.
> Removing works, but as soon as I re-install it dies again.
>
> I was able to get apport working again by clearing /var/crash. I am
> going to put a tail on syslog to see it happening live.
>
> This is Bind9, so that is why I am reporting it also to Security team.
>
> I am also getting 'audit' failures that come from AppArmor. I believe
> these revolve around the snapd subsystem. They occurred in 18.04.4,
> which was why I was eager to try an update.
>
> Thanks in advance. I'll be glad to try a patch.
>
> ProblemType: Package
> DistroRelease: Ubuntu 20.04
> Package: dms-core 1.0.8.1-1ubuntu2
> ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
> Uname: Linux 5.4.0-26-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27
> Architecture: amd64
> CasperMD5CheckResult: skip
> Date: Fri Apr 24 11:20:51 2020
> ErrorMessage: installed dms-core package post-installation script
> subprocess returned error exit status 3
> InstallationDate: Installed on 2020-04-24 (0 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
> 3.8.2-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
> 2.7.17-4
> RelatedPackageVersions:
> dpkg 1.19.7ubuntu3
> apt 2.0.2
> SourcePackage: dms
> Title: package dms-core 1.0.8.1-1ubuntu2 failed to install/upgrade:
> installed dms-core package post-installation script subprocess returned
> error exit status 3
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dms/+bug/1874901/+subscriptions
>

--
Don Wilde
*******************************************...

[Launchpad Janitor (janitor)]

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