software-center crashed with SIGSEGV in g_main_context_dispatch()

[Daniël]

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

software-center:
  Installed: 13.07-0ubuntu4
  Candidate: 13.07-0ubuntu4
  Version table:
 *** 13.07-0ubuntu4 0
        500 http://be.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

Expected: installed clementine

happened: installed clementine but also crashed right after

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.07-0ubuntu4
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jul 27 08:08:54 2013
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2013-07-27 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
SegvAnalysis:
 Segfault happened at: 0x7f9ca582f623: lock addl $0x1,0x48(%rax)
 PC (0x7f9ca582f623) ok
 source "$0x1" ok
 destination "0x48(%rax)" (0x7562752f6d6f6376) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? () from /usr/lib/libgnome-menu-3.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: software-center crashed with SIGSEGV in g_main_context_dispatch()
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 #1193839, 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.