software-center crashed with SIGSEGV

Bug #1054601 reported by Sasa Paporovic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Software-Center crashed just right after starting it with unity.

Steps to reproduce:

1.Click on the software-center icon
2.Wait some seconds
3.See it crashing

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: software-center 5.3.14.2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 22 16:34:29 2012
Disassembly: => 0x7f74ce6dfd20: Cannot access memory at address 0x7f74ce6dfd20
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 PATH=(custom, no username)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f74ce6dfd20: Cannot access memory at address 0x7f74ce6dfd20
 PC (0x7f74ce6dfd20) ok
 SP (0x7fffc5617f60) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: software-center
Stacktrace:
 #0 0x00007f74ce6dfd20 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffc5617f60
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 8822):
 #0 0x00007f74def2c9e3 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f74c5144e20
Title: software-center crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f74ce6dfd20 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffc5617f60
StacktraceSource: #0 0x00007f74ce6dfd20 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 8822):
 #0 0x00007f74def2c9e3 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f74c5144e20

Changed in software-center (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libfribidi0: package version 0.19.2-3 dbgsym version 0.19.2-1
libglib2.0-bin version 2.33.14-1 required, but 2.33.14-1svn2 is available
outdated debug symbol package for libglib2.0-bin: package version 2.33.14-1svn2 dbgsym version 2.33.14-1
outdated debug symbol package for libcap-ng0: package version 0.6.6-2ubuntu1 dbgsym version 0.6.6-1ubuntu1
libglib2.0-0 version 2.33.14-1 required, but 2.33.14-1svn2 is available
libglib2.0-data version 2.33.14-1 required, but 2.33.14-1svn2 is available
outdated debug symbol package for libfile-fcntllock-perl: package version 0.14-2 dbgsym version 0.14-1build1
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for usbutils: package version 1:005-3 dbgsym version 1:005-1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-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.