software-center crashed with SIGSEGV in PyGILState_Ensure()

[Darren Weslow]

The software center crashed, Unsure of why the application launched in the first place.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.4
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Dec 30 02:28:36 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center v-sim-common/V_Sim
SegvAnalysis:
 Segfault happened at: 0x4dbe38: mov 0x8(%rbp),%rax
 PC (0x004dbe38) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SoftwareCenterLog:
 2011-12-30 02:26:56,108 - softwarecenter.ui.gtk3.em - INFO - EM's: 17 13 20
 2011-12-30 02:27:00,655 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file
 2011-12-30 02:27:02,409 - softwarecenter.ui.gtk3.utils - INFO - Softwarecenter style provider for ambiance Gtk theme: /usr/share/software-center/ui/gtk3/css/softwarecenter.css
 2011-12-30 02:27:08,262 - softwarecenter.ui.gtk3.app - INFO - software-center-agent finished with status 0
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-30 (0 days ago)
UserGroups: adm lpadmin sambashare sudo

[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.