software-center crashed with SIGSEGV

Bug #523348 reported by IKT
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: software-center

Going into the software centre, clicking on a program, clicking on the screenshot in the details window, then it freezes/crashes.

ProblemType: Crash
Architecture: i386
Date: Thu Feb 18 04:37:59 2010
Disassembly: 0x74a5200: Cannot access memory at address 0x74a5200
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
InterpreterPath: /usr/bin/python2.6
Package: software-center 1.1.11
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0x74a5200: Cannot access memory at address 0x74a5200
 PC (0x074a5200) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: software-center
Stacktrace:
 #0 0x074a5200 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf91d13c
StacktraceTop: ?? ()
Title: software-center crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
IKT (ikt) wrote :
visibility: private → public
Revision history for this message
IKT (ikt) wrote :

USC is no longer suggesting an apport report but instead when I click close this appears in messages log:

Feb 18 04:59:36 ikt-laptop kernel: [ 168.893328] software-center[1431]: segfault at 78 ip 02160200 sp bfea85c0 error 4 in libwebkit-1.0.so.2.15.1[1d3e000+d3a000]
Feb 18 05:00:33 ikt-laptop kernel: [ 225.186748] software-center[1495]: segfault at 78 ip 02bb2200 sp bf83b8b0 error 4 in libwebkit-1.0.so.2.15.1[2790000+d3a000]

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

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

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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

software-center: installed version 1.1.11, latest version: 1.1.12

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-i386-retrace
Revision history for this message
Guillaume Pascal (guigui14100-deactivatedaccount) wrote :

I have same problem in the last version

IKT (ikt)
Changed in software-center (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
IKT (ikt) wrote :

guigui14100: Is that version 1.1.12? Are you able to attach your information to this report or submit another one?

Revision history for this message
Omer Akram (om26er) wrote :

Does the crash happen when you close the screenshot window? If yes then its bug#518127

Revision history for this message
IKT (ikt) wrote : Re: [Bug 523348] Re: software-center crashed with SIGSEGV

https://bugs.launchpad.net/bugs/518127

*Not allowed here*

Sorry, you don't have permission to access this page.

You are logged in as IKT.

??

On Thu, Feb 18, 2010 at 4:32 PM, Omer Akram <email address hidden> wrote:
>
> Does the crash happen when you close the screenshot window? If yes then
> its bug#518127
>
> --
> software-center crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/523348
> You received this bug notification because you are a direct subscriber
> of the bug.

Revision history for this message
Omer Akram (om26er) wrote :

its public now

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.