package python3-jinja2 2.10-1 failed to install/upgrade: installed python3-jinja2 package post-installation script subprocess returned error exit status 139

Bug #1770837 reported by Dick Taylor
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python3.6 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Installed during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-jinja2 2.10-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 11 18:00:57 2018
DuplicateSignature:
 package:python3-jinja2:2.10-1
 Setting up python3-jinja2 (2.10-1) ...
 Segmentation fault
 dpkg: error processing package python3-jinja2 (--configure):
  installed python3-jinja2 package post-installation script subprocess returned error exit status 139
ErrorMessage: installed python3-jinja2 package post-installation script subprocess returned error exit status 139
InstallationDate: Installed on 2014-01-06 (1586 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
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.1
SourcePackage: jinja2
Title: package python3-jinja2 2.10-1 failed to install/upgrade: installed python3-jinja2 package post-installation script subprocess returned error exit status 139
UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

Revision history for this message
Dick Taylor (taylor-dick) wrote :
tags: removed: need-duplicate-check
Revision history for this message
James Page (james-page) wrote :

[ 3606.252220] py3compile[30831]: segfault at 8 ip 0000000000443e5a sp 00007ffc26c3f2c8 error 6 in python3.6[400000+3c1000]

affects: jinja2 (Ubuntu) → python3.6 (Ubuntu)
Revision history for this message
James Page (james-page) wrote :

Moving bug over to python3.6 as it certainly should not be segfaulting on a py3compile call.

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

Other bug subscribers

Remote bug watches

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