command-not-found crashed with SIGABRT in Py_FatalError()

Bug #1050584 reported by Josh Dalziel on 2012-09-13
This bug affects 11 people
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
python3.2 (Ubuntu)

Bug Description

Just popped up while using duma to run a executable.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: command-not-found 0.3ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Thu Sep 13 12:41:14 2012
ExecutablePath: /usr/lib/command-not-found
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/command-not-found -- 9
 PATH=(custom, no user)
Signal: 6
SourcePackage: command-not-found
 raise () from /lib/i386-linux-gnu/
 abort () from /lib/i386-linux-gnu/
 Py_FatalError ()
 Py_InitializeEx ()
 Py_Initialize ()
Title: command-not-found crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-31 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Josh Dalziel (josh-dalziel) wrote :

 Py_FatalError (msg=msg@entry=0x8185834 "Py_Initialize: can't initialize sys standard streams") at ../Python/pythonrun.c:2187
 Py_InitializeEx (install_sigs=1) at ../Python/pythonrun.c:312
 Py_Initialize () at ../Python/pythonrun.c:332
 Py_Main (argc=argc@entry=4, argv=argv@entry=0x906d008) at ../Modules/main.c:637
 main (argc=4, argv=0xbfac3ef4) at ../Modules/python.c:65

Changed in command-not-found (Ubuntu):
importance: Undecided → Medium
summary: - command-not-found crashed with SIGABRT in raise()
+ command-not-found crashed with SIGABRT in Py_FatalError()
tags: removed: need-i386-retrace
visibility: private → public
Barry Warsaw (barry) wrote :

Can you provide the exact command line you used to provoke this crash? Also, though I'm not as familiar with duma as I once was with electric fence, is it possible that duma is messing with the environment enough to cause havoc with Python's std*?

Launchpad Janitor (janitor) wrote :

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

Changed in command-not-found (Ubuntu):
status: New → Confirmed
Changed in python3-defaults (Ubuntu):
status: New → Confirmed
Josh Dalziel (josh-dalziel) wrote :

No expert here, but I think what happened for me was.. Trying to profile a application with out the a duma library linked. I got my error while profiling a python script that crash with large data sets. I think other users are not having the same problem as I am.

Scott Kitterman (kitterman) wrote :

Python3 is just a symlink to python3.2 in the version this bug was reported in, so if there is a python3 issue, it's in python3.2, not python3-defaults. If you find this also occurs with python3.3, you can add python3.3 to th bug by marking it as also being affected by this issue.

affects: python3-defaults (Ubuntu) → python3.2 (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers