package libmspack0 0.5-1ubuntu0.16.04.1 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libmspack.so.0.1.0.dpkg-new': Read-only file system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libmspack (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Showed when running updates without any prior warning nor complain in the log files.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libmspack0 0.5-1ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
libmspack0: Install
libmspack0: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 2 07:35:18 2018
Dependencies:
gcc-6-base 6.0.1-0ubuntu1
libc6 2.23-0ubuntu10
libgcc1 1:6.0.1-0ubuntu1
DpkgTerminalLog:
Preparing to unpack .../libmspack0_
Unpacking libmspack0:amd64 (0.5-1ubuntu0.
dpkg: error processing archive /var/cache/
unable to securely remove '/usr/lib/
DuplicateSignature:
package:
Unpacking libmspack0:amd64 (0.5-1ubuntu0.
dpkg: error processing archive /var/cache/
unable to securely remove '/usr/lib/
ErrorMessage: unable to securely remove '/usr/lib/
RelatedPackageV
dpkg 1.18.4ubuntu1.4
apt 1.2.27
SourcePackage: libmspack
Title: package libmspack0 0.5-1ubuntu0.
UpgradeStatus: Upgraded to xenial on 2016-09-23 (678 days ago)
tags: | removed: need-duplicate-check |
Thank you for taking the time to file a bug report.
Based on the terminal log it looks like you have a read-only filesystem. That would cause the failures you are seeing. A better question is why you have a read-only filesystem.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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://