package libasprintf0v5:amd64 0.19.7-2ubuntu3.1 failed to install/upgrade: package libasprintf0v5:amd64 is already installed and configured

[alejandro]

no more

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libasprintf0v5:amd64 0.19.7-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Tue Dec 4 00:03:04 2018
Dependencies:
 gcc-5-base 5.4.0-6ubuntu1~16.04.11
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 libstdc++6 5.4.0-6ubuntu1~16.04.11
DuplicateSignature:
 package:libasprintf0v5:amd64:0.19.7-2ubuntu3.1
 Processing triggers for install-info (6.1.0.dfsg.1-5) ...
 dpkg: error processing package udev (--configure):
  package udev is already installed and configured
ErrorMessage: package libasprintf0v5:amd64 is already installed and configured
InstallationDate: Installed on 2018-12-02 (48 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt 1.2.29
SourcePackage: dpkg
Title: package libasprintf0v5:amd64 0.19.7-2ubuntu3.1 failed to install/upgrade: package libasprintf0v5:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

[Alex Murray (alexmurray)]

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.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1812544, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.