software-center crashed with SIGSEGV

Bug #564856 reported by Valldis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: software-center

after uninstalling an application, it suddenly got stuck.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: software-center 2.0
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
CheckboxSubmission: 3aaf7b1364941d38481329db0f4bce78
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
CrashCounter: 1
Date: Fri Apr 16 19:07:35 2010
Disassembly: => 0x7fad30c12349: Cannot access memory at address 0x7fad30c12349
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANG=ca_ES.utf8
 SHELL=/bin/bash
Signal: 11
SourcePackage: software-center
Stacktrace:
 #0 0x00007fad30c12349 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffba397f90
StacktraceTop: ?? ()
Title: software-center crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x7fad30c12349: Cannot access memory at address 0x7fad30c12349
 PC (0x7fad30c12349) ok
 SP (0x7fffba397f90) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
Valldis (valldis) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fad30c12349 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffba397f90
StacktraceTop: ?? ()
ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Kees Cook (kees)
description: updated
Revision history for this message
Omer Akram (om26er) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in software-center (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
visibility: private → public
Revision history for this message
Omer Akram (om26er) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Kiwinote (kiwinote) wrote :

Hi!

Thanks for your bug report and sorry for the delayed response.
As you may be aware, during each cycle a lot of work goes into
software-center. However, over time we build up a long list of
bugs which are most likely no longer present in recent versions
of software-center.

In an attempt to clean up the bug list for software-center I am
expiring this bug because it meets one or more of the following
criteria:
- it would seem quite likely that this bug is no longer present
  in recent versions of software-center,
- the bug report does not contain sufficient information for us
  to reproduce and/or fix the bug,
- the issue is most likely in an external piece of code and has
  most likely been fixed since the bug was reported.

If you experience any problems in recent development versions
of software-center, please do continue to report new bugs.
Thanks again for your help!

Changed in software-center (Ubuntu):
status: Incomplete → Expired
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.