package libjpeg-turbo8-dev (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/include/jerror.h' before installing another version: Read-only file system

[Arup Sinha]

during installation of hp printer

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libjpeg-turbo8-dev (not installed)
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libjpeg9:amd64: Install
 libjpeg-progs:amd64: Install
 libjpeg-turbo8-dev:amd64: Install
 libjpeg8-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Nov 9 08:17:11 2018
DuplicateSignature:
 package:libjpeg-turbo8-dev:(not installed)
 Unpacking libjpeg9:amd64 (1:9b-2) ...
 dpkg: error processing archive /var/cache/apt/archives/libjpeg9_1%3a9b-2_amd64.deb (--unpack):
  unable to clean up mess surrounding './usr/lib/x86_64-linux-gnu/libjpeg.so.9.2.0' before installing another version: Read-only file system
ErrorMessage: unable to clean up mess surrounding './usr/include/jerror.h' before installing another version: Read-only file system
InstallationDate: Installed on 2018-11-07 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.6
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: unable to clean up mess surrounding './usr/include/jerror.h' before installing another version: Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]