software-center crashed with signal 5 in _XReadEvents()

[James Tait]

This has happened a couple of times now. I start Software Centre, it presents the initial display, then goes grey, presumably updating something in the background. Then it crashes and I restart it and everything's fine. There may be a correlation with me being impatient sometimes, and clicking menu items even though the window is still grey, but nothing I could call reliably reproducible.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.09-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Fri Sep 20 10:18:06 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2013-09-11 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: software-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: software-center crashed with signal 5 in _XReadEvents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1211887, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.