package gufw 16.04.1-0ubuntu1.1 failed to install/upgrade: package gufw is already installed and configured

[Maksymilian Wastag]

...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gufw 16.04.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: i386
Date: Fri Mar 20 03:03:17 2020
DuplicateSignature:
 package:gufw:16.04.1-0ubuntu1.1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package gufw (--configure):
  package gufw is already installed and configured
ErrorMessage: package gufw is already installed and configured
InstallationDate: Installed on 2020-03-19 (0 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt 1.2.29ubuntu0.1
SourcePackage: dpkg
Title: package gufw 16.04.1-0ubuntu1.1 failed to install/upgrade: package gufw is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

[Mark Morlino (markmorlino)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Seth Arnold (seth-arnold)]

Hello, looking through your logs it looks like your machine has significant problems. Some of them, like the CPU overheating, may or may not be something you can solve by cleaning the fans or heatsinks or making sure any fans or heatsinks are working.

Perhaps the heat problems have caused several of the memory errors in your logs.

It appears you may also have problems with your disks; I can't tell what, exactly, maybe disks, maybe controller, maybe cables, maybe power.

I don't know what this bug is for, but it may or may not be related to what looks like hardware problems.

Thanks