package linux-headers-4.15.0-32 4.15.0-32.35~16.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h' para '/usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h.dpkg-new': fim de ficheiro ou stream inesperado

[Gustavo Malheiros]

I received an error advise and came here to relate it for you.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-32 4.15.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Tue Oct 16 11:40:17 2018
ErrorMessage: não pode copiar dados extráidos para './usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h' para '/usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h.dpkg-new': fim de ficheiro ou stream inesperado
InstallationDate: Installed on 2017-07-20 (453 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageArchitecture: all
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
 apt 1.6.3ubuntu0.1
SourcePackage: linux-hwe
Title: package linux-headers-4.15.0-32 4.15.0-32.35~16.04.1 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h' para '/usr/src/linux-headers-4.15.0-32/include/dt-bindings/clock/exynos5260-clk.h.dpkg-new': fim de ficheiro ou stream inesperado
UpgradeStatus: Upgraded to bionic on 2018-08-18 (59 days ago)

[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.]