software-center crashed with SIGSEGV in PyGILState_Ensure()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Had clicked to install gparted the button shaded but nothing happened, after waiting some few minutes, clicked to return to home page of software center , closed the program, was preparing to load from terminal , when received crash notification.
All available updates had been applied before attempting to use software center. ubuntu 12.04 in unity desktop, intel i7 , 8g ram, 5470 amd radeon, 500 gb 7200 rpm seagate internal hd . Nothing else I can add. Crash notification after software center was closed approximately 20-30 seconds
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.3
ProcVersionSign
Uname: Linux 3.2.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Dec 4 01:27:46 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
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/
g_datalist_clear () from /lib/x86_
g_object_unref () from /usr/lib/
Title: software-center crashed with SIGSEGV in PyGILState_Ensure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #894721, 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.