package libpcap0.8:i386 1.9.1-3 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 | |
---|---|---|---|---|---|
libpcap (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When installing curl & node.js I am getting this error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpcap0.8:i386 1.9.1-3
ProcVersionSign
Uname: Linux 5.4.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
libcurl4:amd64: Install
curl:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckR
Date: Tue Jan 5 20:58:25 2021
DpkgHistoryLog:
Start-Date: 2021-01-05 20:58:21
Commandline: apt install curl
Requested-By: abhishek (1000)
Install: curl:amd64 (7.68.0-1ubuntu2.4)
Upgrade: libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.4)
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2020-11-15 (51 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitec
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: libpcap
Title: package libpcap0.8:i386 1.9.1-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to file a bug report.
Based on what I can find in the attached logs, I cannot really understand the sequence of commands that may have led to this error. I tried reproducing it in a container here, making sure to enable i386 first, but everything (curl, nodejs and libpcap0.8) install correctly and without problems. Could you please provide detailed instructions on how to reproduce this issue, or at least tell us what you did that triggered this error?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
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".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://