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

[Adam Conrad]

Hello tolostoi, or anyone else affected,

Accepted lsb into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lsb/4.0-0ubuntu26.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from
verification-needed to verification-done.  If it does not, change the
tag to verification-failed.  In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lsb (Ubuntu Quantal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: lsb (Ubuntu Precise)
       Status: In Progress => Fix Committed

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

Title:
  lsb_release crashed with SIGABRT in Py_FatalError()

Status in “lsb” package in Ubuntu:
  Fix Released
Status in “lsb” source package in Precise:
  Fix Committed
Status in “lsb” source package in Quantal:
  Fix Committed
Status in “lsb” source package in Raring:
  Fix Released

Bug description:
  = SRU =

  All Python system scripts should use -Es to ignore $PYTHON* envars and
  to ignore the user's site directory.  This is a general
  recommendation.

  [Test Case]
  $ PYTHONHOME=/does/not/exist lsb_release
  -> crashes without the fix
  -> works correctly with the fix

  [Regression Potential]
  None expected.

  = Details =

  During the installation process of either VMware Player major version
  4 or 5 you will receive a crash report regarding lsb-release as VMware
  ships a version of python 2 with the installer and the installation
  process calls lsb-release which uses python 3.

  I'm just login, and the message to some application 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/lsb/+bug/938869/+subscriptions