software-center crashed with SIGSEGV in PyGILState_Ensure()

[Andrew Somerville]

Looks similar to other bugs, expect I got this bug when clicking on a package I downloaded (Mainline Kernel headers).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.3.1
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: 1e30f81ce28ba1c34b3ec9f8f96eb1ea
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Sun Dec 11 13:38:32 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Downloads/linux-headers-3.2.0-030200rc5_3.2.0-030200rc5.201112091935_all.deb
SegvAnalysis:
 Segfault happened at: 0x4dc0b8: mov 0x8(%rbp),%rax
 PC (0x004dc0b8) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? ()
 PyGILState_Ensure ()
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gobject/_gobject.so
 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: software-center crashed with SIGSEGV in PyGILState_Ensure()
UpgradeStatus: Upgraded to precise on 2011-12-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #902744, 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.