Ubuntu
apt package

package libapt-inst2.0:i386 1.4.6~17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Bug #1719180 reported by George Schmoll on 2017-09-24

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	apt (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Failed to install

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libapt-inst2.0:i386 1.4.6~17.04.1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic i686
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
emacs-snapshot-el:i386: Install
emacs-snapshot:i386: Install
emacs-snapshot-common:i386: Install
NULL: ConfigurePending
Architecture: i386
Date: Sun Sep 24 06:59:50 2017
DuplicateSignature:
package:libapt-inst2.0:i386:1.4.6~17.04.1
Unpacking emacs-snapshot-common (20170923:93645-c0af83b~ubuntu17.04.1) over (20170920:93641-3a09343~ubuntu17.04.1) ...
dpkg: error processing package libapt-inst2.0:i386 (--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 2017-01-31 (235 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
RelatedPackageVersions:
dpkg 1.18.10ubuntu2
apt 1.4.6~17.04.1
SourcePackage: apt
Title: package libapt-inst2.0:i386 1.4.6~17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: Upgraded to zesty on 2017-04-15 (162 days ago)

Tags:

Revision history for this message

George Schmoll (gschmoll) wrote on 2017-09-24:

Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Df.txt Edit (648 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (90.1 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (15.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (850 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (103.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (711 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2017-09-24

tags:

removed: need-duplicate-check

Revision history for this message

Julian Andres Klode (juliank) wrote on 2017-09-24:

AFAICT from the log, you broke your system when you interrupted an upgrade occuring on 2017-09-14 09:09:30. After unattended-upgrades failed to upgrade tcpdump earlier that day, you tried to upgrade

libapt-inst2.0:i386 (1.4, 1.4.6~17.04.1), apt:i386 (1.4, 1.4.6~17.04.1), tcpdump:i386 (4.9.0-2ubuntu2, 4.9.2-0ubuntu0.17.04.2), libapt-pkg5.0:i386 (1.4, 1.4.6~17.04.1), apt-utils:i386 (1.4, 1.4.6~17.04.1), apt-transport-https:i386 (1.4, 1.4.6~17.04.1)

but cancelled it at some point. Now you have to repair it: Run apt install --reinstall libapt-inst2.0:i386 I guess.

Changed in apt (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuapt package