lsb_release crashed with SIGABRT in Py_FatalError()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lsb (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Encountered on every login
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: lsb-release 4.0-0ubuntu23
ProcVersionSign
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Tue Aug 28 13:32:58 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_DK.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: lsb
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
Py_FatalError ()
?? ()
Py_InitializeEx ()
Title: lsb_release crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-16 (19 days ago)
UserGroups:
visibility: | private → public |
Changed in lsb (Ubuntu): | |
status: | Confirmed → Triaged |
This crash has the same stack trace characteristics as bug #938869. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.