software-center crashed with SIGSEGV

Bug #904068 reported by Petr E. Antonov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Medium
Unassigned

Bug Description

Crashed after exiting from hibernation mode.

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 i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Dec 14 00:26:11 2011
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 cheese
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x8119f70: mov 0x4(%ebx),%edx
 PC (0x08119f70) 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
Stacktrace:
 #0 0x08119f70 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbff1ef4c
StacktraceTop: ?? ()
Title: software-center crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2011-12-12 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Petr E. Antonov (antpeter) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 new_threadstate (interp=0x0, init=1) at ../Python/pystate.c:200
         tstate = 0xaecbd80
 Cannot access memory at address 0xbff1ef4c
StacktraceTop: new_threadstate (interp=0x0, init=1) at ../Python/pystate.c:200

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in software-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.