lsb_release crashed with SIGSEGV in PyObject_GC_UnTrack()

[cacula]

I don't know

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: lsb-release 4.0-0ubuntu20
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 19:00:57 2012
ExecutablePath: /usr/bin/lsb_release
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lsb_release -c -s
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4effd2 <PyObject_GC_UnTrack+34>: mov %rdx,0x8(%rax)
 PC (0x004effd2) ok
 source "%rdx" ok
 destination "0x8(%rax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: lsb
StacktraceTop:
 PyObject_GC_UnTrack ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: lsb_release crashed with SIGSEGV in PyObject_GC_UnTrack()
UpgradeStatus: Upgraded to precise on 2012-02-23 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 PyObject_GC_UnTrack ()
 tupledealloc ()
 code_dealloc ()
 func_dealloc ()
 dict_dealloc ()

[Launchpad Janitor (janitor)]

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