package libavfilter3:amd64 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Bug #1486302 reported by Guido
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libav (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Error message prompted when trying to update software from the updates manager

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libavfilter3:amd64 6:9.18-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Tue Aug 18 22:19:06 2015
DuplicateSignature: package:libavfilter3:amd64:6:9.18-0ubuntu0.14.04.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2014-11-18 (273 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: libav
Title: package libavfilter3:amd64 6:9.18-0ubuntu0.14.04.1 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)

Revision history for this message
Guido (gromadzyn) wrote :
tags: removed: need-duplicate-check
Mathew Hodson (mhodson)
Changed in libav (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Reinhard Tartler (siretart) wrote :

Is this reproducible? It sounds like something that can be resolved following http://askubuntu.com/questions/422696/package-is-in-a-very-bad-inconsistent-state

Changed in libav (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libav (Ubuntu) because there has been no activity for 60 days.]

Changed in libav (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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