software-center crashed with SIGSEGV in PyGILState_Ensure()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed while i tried to import the medibuntu keyring with:
sudo apt-key adv --recv-keys --keyserver keyserver.
Host: Server 2008 R2
Virtualbox: 4.1.8
Guest: Precise 64 bit (updated from Oneiric)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.4
ProcVersionSign
Uname: Linux 3.2.0-6-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Dec 20 12:57:25 2011
ExecutablePath: /usr/share/
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
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-20 12:57:05,397 - softwarecenter.
2011-12-20 12:57:07,088 - softwarecenter.
2011-12-20 12:57:07,540 - softwarecenter.
2011-12-20 12:57:13,485 - softwarecenter.
SourcePackage: software-center
StacktraceTop:
?? ()
PyGILState_Ensure ()
?? () from /usr/lib/
g_datalist_clear () from /lib/x86_
?? () from /usr/lib/
Title: software-center crashed with SIGSEGV in PyGILState_Ensure()
UpgradeStatus: Upgraded to precise on 2011-12-13 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.