software-center crashed with SIGSEGV in PyGILState_Ensure()

Bug #904898 reported by Gabor Toth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just got this crash while focus was on another application. There is a number of reports of it but as these are on 11.04 or 12.04 i am reporting it here for 11.10.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-center 5.0.2ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Thu Dec 15 19:21:37 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center gnomad2/Gnomad\ 2
SegvAnalysis:
 Segfault happened at: 0x8119f10: mov 0x4(%ebx),%edx
 PC (0x08119f10) ok
 source "0x4(%ebx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? ()
 PyGILState_Ensure ()
 pyglib_gil_state_ensure () from /usr/lib/libpyglib-gi-2.0-python2.7.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gobject/_gobject.so
 g_datalist_clear (datalist=0x9e26d40) at /build/buildd/glib2.0-2.30.0/./glib/gdataset.c:282
Title: software-center crashed with SIGSEGV in PyGILState_Ensure()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (62 days ago)
UserGroups: adm admin audio cdrom dialout dip lpadmin netdev plugdev sambashare scanner vboxusers video

Revision history for this message
Gabor Toth (gabor-me) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #893501, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.