Ubuntu
software-center package

software-center crashed with SIGSEGV in free()

Bug #633121 reported by Pierre-Henri Berard on 2010-09-08

30

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	software-center (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: software-center

Software-center crashed after clicing on inventury on Ubuntu One.

Description: Ubuntu maverick (development branch)
Release: 10.10

software-center:
  Installé : 2.1.16.1
  Candidat : 2.1.16.1
Table de version :
*** 2.1.16.1 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: software-center 2.1.16.1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 8 14:16:49 2010
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
LANGUAGE=fr_FR:fr:en
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ffcc14dac2d <free+29>: mov -0x8(%rdi),%rsi
PC (0x7ffcc14dac2d) ok
source "-0x8(%rdi)" (0xa000f6b8) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
free () from /lib/libc.so.6
ffi_call_unix64 () from /usr/lib/python2.6/lib-dynload/_ctypes.so
ffi_call () from /usr/lib/python2.6/lib-dynload/_ctypes.so
_CallProc () from /usr/lib/python2.6/lib-dynload/_ctypes.so
?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: software-center crashed with SIGSEGV in free()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Tags:

Revision history for this message

Pierre-Henri Berard (pierreberard) wrote on 2010-09-08:

#1

Dependencies.txt Edit (6.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (890 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (81.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (828 bytes, text/plain; charset="utf-8")
Registers.txt Edit (795 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (6.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (15.1 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-10:

#2

StacktraceTop:
free () from /lib/libc.so.6
ffi_call_unix64 ()
ffi_call ()
_CallProc (pProc=<value optimized out>,
CFuncPtr_call (self=0x3e73ae0, inargs=0x3e92dd0,

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-10: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-10: ThreadStacktrace.txt

#4

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

Changed in software-center (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2011-09-09:

#5

Thanks for reporting this error, and we're sorry we didn't get to it earlier.

The code has changed a lot since your report. So it's quite likely this problem has been fixed anyway, and Ubuntu Software Center will be better off if engineers spend their time on problems that people have been reporting more recently. If you still do experience the problem, please reopen this report and provide exact steps to reproduce it. Thanks for your understanding.

Changed in software-center (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-11-09:

#6

[Expired for software-center (Ubuntu) because there has been no activity for 60 days.]

Changed in software-center (Ubuntu):
status:	Incomplete → Expired

Khalid Saleh (khalidsalehab) on 2014-03-31

Changed in software-center (Ubuntu):
status:	Expired → New

Report a bug

This report contains Public information

Everyone can see this information.

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.