[Bug 938869] Re: lsb_release crashed with SIGABRT in Py_FatalError()

[Matthias Klose]

looks like the vmware installer uses a partial python2.x environment,
and then calling everything else with this environment. when lsb_release
is called, then they try to run a python3 with a partial python2.x
library, which is ... interesting.

not seen on other distros, because lsb_release isn't implemented there
in python. not seen in precise (at least in the final release), because
lsb_release uses python2.x there, and they don't break it as bad as in
quantal.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python3.2 in Ubuntu.
https://bugs.launchpad.net/bugs/938869

Title:
  lsb_release crashed with SIGABRT in Py_FatalError()

Status in “python3.2” package in Ubuntu:
  Triaged

Bug description:
  I'm just login, and the message to some aplication crashed pops up.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: lsb-release 4.0-0ubuntu19
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  Date: Wed Feb 22 13:45:24 2012
  ExecutablePath: /usr/bin/lsb_release
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/lsb_release -sd
  Signal: 6
  SourcePackage: lsb
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   Py_FatalError ()
   ?? ()
   Py_InitializeEx ()
  Title: lsb_release crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-02-17 (5 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.2/+bug/938869/+subscriptions