Ubuntu
python3.6 package

python3.6 crashed with SIGABRT in Py_FatalError()

Bug #1727427 reported by Simon Friedberger on 2017-10-25

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	python3.6 (Ubuntu)	Expired	Medium	Unassigned

Bug Description

I don't fucking know I just got a popup.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: python3.6-minimal 3.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: i3
Date: Wed Oct 25 10:56:18 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/python3.6
InstallationDate: Installed on 2016-06-01 (510 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/bin/python3 xmlstuff.py crash/42.1193292
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
Signal: 6
SourcePackage: python3.6
StacktraceTop:
Py_FatalError ()
?? ()
Py_Main ()
main ()
Title: python3.6 crashed with SIGABRT in Py_FatalError()
UpgradeStatus: Upgraded to artful on 2017-05-07 (170 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark

Tags:

Revision history for this message

Simon Friedberger (simon-ubuntu-p) wrote on 2017-10-25:

#1

Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (947 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (167.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (322 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (4.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (741 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1016 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-25:

#2

StacktraceTop:
Py_FatalError (msg=msg@entry=0x65a020 "Py_Initialize: can't initialize sys standard streams") at ../Python/pylifecycle.c:1466
_Py_InitializeEx_Private (install_sigs=install_sigs@entry=1, install_importlib=install_importlib@entry=1) at ../Python/pylifecycle.c:454
_Py_InitializeEx_Private (install_importlib=1, install_sigs=1) at ../Python/pylifecycle.c:481
Py_InitializeEx (install_sigs=1) at ../Python/pylifecycle.c:474
Py_Initialize () at ../Python/pylifecycle.c:480

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-25: Stacktrace.txt

#3

Stacktrace.txt Edit (2.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-25: StacktraceSource.txt

#4

StacktraceSource.txt Edit (2.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-25: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (2.5 KiB, text/plain)

Changed in python3.6 (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Matthias Klose (doko) wrote on 2018-04-28:

#6

please attach your xmlstuff.py script

Changed in python3.6 (Ubuntu):
status:	New → Incomplete
information type:	Private → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-06-28:

#7

[Expired for python3.6 (Ubuntu) because there has been no activity for 60 days.]

Changed in python3.6 (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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