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

Bug #1785256 reported by Georges Giralt
10
This bug affects 1 person
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.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
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_0.5-1ubuntu0.16.04.2_amd64.deb ...
 Unpacking libmspack0:amd64 (0.5-1ubuntu0.16.04.2) over (0.5-1ubuntu0.16.04.1) ...
 dpkg: error processing archive /var/cache/apt/archives/libmspack0_0.5-1ubuntu0.16.04.2_amd64.deb (--unpack):
  unable to securely remove '/usr/lib/x86_64-linux-gnu/libmspack.so.0.1.0.dpkg-new': Read-only file system
DuplicateSignature:
 package:libmspack0:0.5-1ubuntu0.16.04.1
 Unpacking libmspack0:amd64 (0.5-1ubuntu0.16.04.2) over (0.5-1ubuntu0.16.04.1) ...
 dpkg: error processing archive /var/cache/apt/archives/libmspack0_0.5-1ubuntu0.16.04.2_amd64.deb (--unpack):
  unable to securely remove '/usr/lib/x86_64-linux-gnu/libmspack.so.0.1.0.dpkg-new': Read-only file system
ErrorMessage: unable to securely remove '/usr/lib/x86_64-linux-gnu/libmspack.so.0.1.0.dpkg-new': Read-only file system
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.27
SourcePackage: libmspack
Title: 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
UpgradeStatus: Upgraded to xenial on 2016-09-23 (678 days ago)

Revision history for this message
Georges Giralt (georges-giralt) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Joshua Powers (powersj) wrote :

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:
http://www.ubuntu.com/support/community

Changed in libmspack (Ubuntu):
status: New → Incomplete
Revision history for this message
Georges Giralt (georges-giralt) wrote : Re: [Bug 1785256] Re: 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

Hello Joshua,

It is funny you write as I was thinking at how to remove the bug report.

It appears that I had a power micro outage which trigered filesystem
errors on the computer that where plugged at this time;

This resulted on one of them by two read-only filesystem and the other
one, crashed.

So the problem is not on ubuntu package but on the power grid company...

Sorry for the inconvenience !

Have a bright day.

Le 06/08/2018 à 18:55, Joshua Powers a écrit :
> 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:
> http://www.ubuntu.com/support/community
>
> ** Changed in: libmspack (Ubuntu)
> Status: New => Incomplete
>

--
"If a man empties his purse into his head, no man can take it away from him.
An investment in knowledge always pays the best interest"

Benjamin Franklin.

Revision history for this message
Joshua Powers (powersj) wrote :

No worries, glad you figured it out :) I will mark this as invalid to close it then.

Thanks you for following up!

Changed in libmspack (Ubuntu):
status: Incomplete → Invalid
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.