package liba52-0.7.4 (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/lib/x86_64-linux-gnu/liba52-0.7.4.so' before installing another version: Read-only file system

Bug #1896432 reported by Akhil Dev

This bug report was converted into a question: question #693028: package liba52-0.7.4 (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/lib/x86_64-linux-gnu/liba52-0.7.4.so' before installing another version: Read-only file system.

8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
a52dec (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

failed to install upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: liba52-0.7.4 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Sep 21 11:14:08 2020
DuplicateSignature:
 package:liba52-0.7.4:(not installed)
 Unpacking gstreamer1.0-libav:amd64 (1.16.2-2) ...
 dpkg: error processing archive /tmp/apt-dpkg-install-Hk3etl/49-gstreamer1.0-libav_1.16.2-2_amd64.deb (--unpack):
  unable to create '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so'): Read-only file system
ErrorMessage: unable to clean up mess surrounding './usr/lib/x86_64-linux-gnu/liba52-0.7.4.so' before installing another version: Read-only file system
InstallationDate: Installed on 2020-09-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: a52dec
Title: package liba52-0.7.4 (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/lib/x86_64-linux-gnu/liba52-0.7.4.so' before installing another version: Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Akhil Dev (akhildev) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Converting to question because filesystem errors are causing filesystem to be remounted as read-only, and that is causing errors in the bug report.

[ 964.667173] EXT4-fs error (device sda4): ext4_validate_inode_bitmap:99: comm dpkg: Corrupt inode bitmap - block_group = 16, inode_bitmap = 524304
[ 964.717342] Aborting journal on device sda4-8.
[ 964.733802] EXT4-fs (sda4): Remounting filesystem read-only

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

Other bug subscribers