submit_usefulness_gtk3.py crashed with SIGSEGV in g_main_context_dispatch()

[Craig Kempson]

Browsing Software Centre, I opted to flag a review or two as useful. The first one went fine, but upon hitting the "Yes" (of "Is this review useful to you, Yes/No?" on the second review, this crash occurred. Not sure if it was from the first or second submit.

Seems bug numbers #1049163 and #1050221 are similar but not identical.

Terminal output upon reproducing it is attached, although I'm not sure how useful it is.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: software-center 5.3.14.2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 21 11:37:57 2012
ExecutablePath: /usr/share/software-center/submit_usefulness_gtk3.py
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/software-center/submit_usefulness_gtk3.py --review-id 51683 --is-useful 1 --parent-xid --datadir /usr/share/software-center/
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x48a5a8: addl $0x1,0x98(%r13)
 PC (0x0048a5a8) ok
 source "$0x1" ok
 destination "0x98(%r13)" (0x00000098) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/python2.7/dist-packages/gi/_glib/_glib.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: submit_usefulness_gtk3.py crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-09-20 (0 days ago)
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 #1049163, 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.