software-center crashed with signal 5

Bug #1165939 reported by Michael Oliver
168
This bug affects 38 people
Affects Status Importance Assigned to Milestone
Ubuntu Software Center
New
Undecided
Unassigned
software-center (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Shortly after loading the content in the window, the package crashes with the following error:

(software-center:22869): Gdk-ERROR **: The program 'software-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 1961 error_code 9 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: software-center 5.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 7 17:46:00 2013
Disassembly: => 0x7fc8dd4502c5: Cannot access memory at address 0x7fc8dd4502c5
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2013-04-05 (2 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: software-center
Stacktrace:
 #0 0x00007fc8dd4502c5 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff414d48f0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 9 (LWP 21496):
 #0 0x00007fc8ded64ca4 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fc8635a9e30
Title: software-center crashed with signal 5
UpgradeStatus: Upgraded to raring on 2013-04-05 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Michael Oliver (moliver-s) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in software-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabian (sanhuesoft) wrote :

¿No solution for this?

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

Stacktrace:
 #0 0x00007fc8dd4502c5 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff414d48f0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 9 (LWP 21496):
 #0 0x00007fc8ded64ca4 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fc8635a9e30

Changed in software-center (Ubuntu):
status: Confirmed → 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 libudev1: package version 198-0ubuntu11.1 dbgsym version 198-0ubuntu11

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
Changed in software-center (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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