software-center crashed with signal 5 in _XReadEvents()

Bug #1240530 reported by Paul Larson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Software center seems to crash on the first launch after install.

I hit this on the saucy rc image from 20131016
The install I had done was amd64 desktop on virtualbox with free software only, no network connection.
Once booted after installing, I attached the network, brought up a terminal and ran apt-get update. Everything looked fine, so I tried running software center and hit this crash.

Running a second time, software center seems to come up ok though.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Wed Oct 16 09:54:54 2013
ExecutablePath: /usr/share/software-center/software-center
ExecutableTimestamp: 1381335773
InstallationDate: Installed on 2013-10-16 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcCwd: /home/a
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.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

Revision history for this message
Paul Larson (pwlars) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
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.