Ubuntu
software-center package

software-center crashed with SIGSEGV in PyObject_SetAttr()

Bug #943436 reported by Wojciech Myszka on 2012-02-29

This bug report is a duplicate of: Bug #914066: software-center crashed with SIGSEGV when installing google-chrome deb file. Edit Remove

12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	software-center (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

After installing google-chrome (taken from google) software center crashed (window in background, no activity)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.10
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Wed Feb 29 18:25:27 2012
Disassembly: => 0x7fa8ec3ea0c0: Cannot access memory at address 0x7fa8ec3ea0c0
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Pobrane/google-chrome-stable_current_amd64.deb
ProcEnviron:
PATH=(custom, no user)
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fa8ec3ea0c0: Cannot access memory at address 0x7fa8ec3ea0c0
PC (0x7fa8ec3ea0c0) ok
SP (0x7fff0ea44ef8) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: software-center
StacktraceTop:
?? ()
?? ()
?? ()
PyObject_SetAttr ()
PyEval_EvalFrameEx ()
Title: software-center crashed with SIGSEGV in PyObject_SetAttr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Wojciech Myszka (myszka-norka) wrote on 2012-02-29:

#1

Dependencies.txt Edit (7.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (76.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (822 bytes, text/plain; charset="utf-8")
Registers.txt Edit (748 bytes, text/plain; charset="utf-8")
SoftwareCenterLog.txt Edit (9.1 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-29:

#2

StacktraceTop:
?? ()
?? ()
?? ()
PyObject_SetAttr ()
PyEval_EvalFrameEx ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-29: Stacktrace.txt

#3

Stacktrace.txt Edit (1.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-29: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (4.5 KiB, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

Gary Lasker (gary-lasker) wrote on 2012-06-27:

#5

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 914066, so it 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
Changed in software-center (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #914066 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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