package libisccc140:amd64 1:9.10.3.dfsg.P4-8ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I was havving issues with my Lock and so I tried to fix some stuff and ran into this, may or may not be a security issue not to sure. Sorry if I may waste your useful time.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libisccc140:amd64 1:9.10.
ProcVersionSign
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed Jun 22 05:17:22 2016
DuplicateSignature:
Processing triggers for libc-bin (2.23-0ubuntu3) ...
dpkg: error processing package libisccc140:amd64 (--configure):
package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2016-06-21 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: bind9
Title: package libisccc140:amd64 1:9.10.
UpgradeStatus: No upgrade log present (probably fresh install)
information type: | Private Security → Public |
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and 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.