lsb_release crashed with SIGABRT in Py_FatalError()

[Thomas M Steenholdt]

Encountered on every login

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: lsb-release 4.0-0ubuntu23
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
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/lsb_release
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/lsb_release -sd
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
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 quantal on 2012-08-16 (19 days ago)
UserGroups:

[Apport retracing service (apport)]

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.

[Apport retracing service (apport)]

StacktraceTop:
 Py_FatalError (msg=msg@entry=0x569f90 "Py_Initialize: Unable to get the locale encoding") at ../Python/pythonrun.c:2187
 initfsencoding.isra.3.20274 () at ../Python/pythonrun.c:776
 Py_InitializeEx (install_sigs=1) at ../Python/pythonrun.c:304
 Py_Initialize () at ../Python/pythonrun.c:332
 Py_Main (argc=argc@entry=3, argv=argv@entry=0x28df010) at ../Modules/main.c:637

[Launchpad Janitor (janitor)]

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

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #938869, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.