package ndiff 7.01-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jon Josef Bjarnason]

occurs when sudo apt-get install nmap
and sudo apt-get install -f

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ndiff 7.01-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 2 17:05:05 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-10-28 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: nmap
Title: package ndiff 7.01-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Robie Basak (racb)]

From log:

Setting up ndiff (7.01-2ubuntu2) ...
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 26, in <module>
    import logging
  File "/usr/lib/python2.7/logging/__init__.py", line 43, in <module>
    import threading
EOFError: EOF read where object expected
dpkg: error processing package ndiff (--configure):
 subprocess installed post-installation script returned error exit status 1

[Robie Basak (racb)]

Thank you for your report.

I cannot reproduce this. In a container, I can install ndiff without errors. It seems to me that your Python installation is corrupt on your system.

Since this looks like local disk corruption or a hardware problem, rather than a bug in Ubuntu, I'm marking this bug as Invalid.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug rather than a problem specific to your system, and then change the bug status back to New.