package apt-xapian-index 0.47ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139. Subsequent attempt succeeded

[Evan Burkitt]

I did the original reinstall because apt-xapian-index crashed. I forced the package to download fresh for the first (failed) reinstall and for the second (successful) one. All three .deb files had the same checksum, though.

Other programs that have crashed this evening: update-notifier, ubuntu-sso-client, apport, dpkg, gnome-shell, oneconf-service and py3compile. All failed while running as daemons or cron jobs, and I became aware of their failures only because of dialog boxes announcing them.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apt-xapian-index 0.47ubuntu13
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 apt-xapian-index:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jul 7 23:24:19 2017
DuplicateSignature:
 package:apt-xapian-index:0.47ubuntu13
 Setting up apt-xapian-index (0.47ubuntu13) ...
 Segmentation fault (core dumped)
 dpkg: error processing package apt-xapian-index (--configure):
  subprocess installed post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit status 139
InstallationDate: Installed on 2015-07-04 (735 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: apt-xapian-index
Title: package apt-xapian-index 0.47ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to zesty on 2017-07-04 (3 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 log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out!

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