software-center crashed with SIGABRT in __assert_fail_base()

[Javier Sanchez Toledano]

Just crashed when starting the session.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.8
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5
Uname: Linux 3.2.0-15-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 11 18:58:45 2012
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: software-center
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: software-center crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0xb746f438 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0xb64c8d39 "ret != inval_id", file=0xb64c8caa "../../src/xcb_io.c", line=528, function=0xb64c8dbe "_XAllocID") at assert.c:94
 __GI___assert_fail (assertion=0xb64c8d39 "ret != inval_id", file=0xb64c8caa "../../src/xcb_io.c", line=528, function=0xb64c8dbe "_XAllocID") at assert.c:103
 _XAllocID (dpy=0x9b456f8) at ../../src/xcb_io.c:528
 XRenderCreateCursor (dpy=0x9b456f8, source=65264418, x=12, y=12) at ../../src/Cursor.c:44
 XcursorImageLoadCursor (dpy=0x9b456f8, image=0xa935200) at ../../src/cursor.c:590

[Launchpad Janitor (janitor)]

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

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/930823

[dino99 (9d9)]

Looks like that issue is now fixed since awhile