package libavcodec54:amd64 (not installed) failed to install/upgrade: package libavcodec54:amd64 is not ready for configuration cannot configure (current status `config-files')

Bug #1438135 reported by Joe Turner
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
muon (Ubuntu)
New
Undecided
Unassigned

Bug Description

14.4

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libavcodec54:amd64 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
Date: Sun Mar 29 18:14:43 2015
DuplicateSignature: package:libavcodec54:amd64:(not installed):package libavcodec54:amd64 is not ready for configuration cannot configure (current status `config-files')
ErrorMessage: package libavcodec54:amd64 is not ready for configuration cannot configure (current status `config-files')
InstallationDate: Installed on 2014-06-11 (291 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: libav
Title: package libavcodec54:amd64 (not installed) failed to install/upgrade: package libavcodec54:amd64 is not ready for configuration cannot configure (current status `config-files')
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Joe Turner (joe-turner) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Aristotelian (bookrt) wrote :

Confirmed, I got the exact same error after attempting to install update.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libav (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

Which program did you use to perfrom the installation?

Changed in libav (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Aristotelian (bookrt) wrote :

I don't remember specifically, but most likely Muon (I am running KDE on the computer in question).

Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

Reassigning to muon. It looks like it calls dpkg in a wrong way.

affects: libav (Ubuntu) → muon (Ubuntu)
Changed in muon (Ubuntu):
status: Incomplete → New
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.