lsb_release crashed with SIGSEGV in move_finalizer_reachable()

[188236]

crashed at startup

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: lsb-release 4.1+Debian11ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Wed Feb 12 20:49:37 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/lsb_release
InstallationDate: Installed on 2014-02-09 (3 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
InterpreterPath: /usr/bin/python3.3
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 -Es /usr/bin/lsb_release -d
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: lsb
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
Title: lsb_release crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: Upgraded to trusty on 2014-02-11 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 move_finalizer_reachable (finalizers=<optimized out>) at ../Modules/gcmodule.c:572
 collect (n_uncollectable=<synthetic pointer>, n_collected=<synthetic pointer>, generation=1) at ../Modules/gcmodule.c:930
 collect_with_callback.28886 (generation=<optimized out>) at ../Modules/gcmodule.c:1048
 collect_generations.28894 () at ../Modules/gcmodule.c:1071

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.