package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

Bug #1739903 reported by C Ulrich
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Performing updates to the system after a fresh install of 16.04 LTS alongside Win 10 Pro.

1) Ubuntu 16.04.03 LTS
2) Pkg Apport 2.20.1-0ubuntu.2.14
3) Installation expected during update
4) Installation failed with status 239

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.14
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CrashReports: 600:0:117:368796:2017-12-23 10:35:04.881695508 -0800:2017-12-23 10:35:05.881695508 -0800:/var/crash/apport.0.crash
Date: Sat Dec 23 10:35:05 2017
DuplicateSignature:
 package:apport:2.20.1-0ubuntu2.14
 Installing new version of config file /etc/init/apport.conf ...
 Segmentation fault
 dpkg: error processing package apport (--configure):
  subprocess installed post-installation script returned error exit status 239
ErrorMessage: subprocess installed post-installation script returned error exit status 239
InstallationDate: Installed on 2017-12-23 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
C Ulrich (war20x) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Evgeniy Permyakov (permeakra) wrote :

same here on a completely fresh install on a new machine

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.