lsb_release crashed with SIGABRT in raise()

Bug #831731 reported by malus
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
lsb (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

happened upon boot of installed system

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lsb-release 4.0-0ubuntu14
ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 16 18:44:43 2011
ExecutablePath: /usr/bin/lsb_release
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python3.2mu
ProcCmdline: /usr/bin/python3 /usr/bin/lsb_release -d
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: lsb
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 Py_FatalError ()
 ?? ()
 Py_InitializeEx ()
Title: lsb_release crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-08-15 (8 days ago)
UserGroups:

Revision history for this message
malus (malus2200) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Py_FatalError (msg=<optimized out>) at ../Python/pythonrun.c:2142
 initfsencoding (interp=<optimized out>) at ../Python/pythonrun.c:749
 Py_InitializeEx (install_sigs=1) at ../Python/pythonrun.c:297
 Py_Main (argc=3, argv=0x284c010) at ../Modules/main.c:597
 main (argc=3, argv=0x7fff07b603d8) at ../Modules/python.c:59

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in lsb (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in lsb (Ubuntu):
status: New → Confirmed
tags: added: precise
tags: added: quantal
visibility: private → public
Revision history for this message
Fila Kolodny (fila) wrote :

Also happened while installing Vmware Workstation.

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.