submit_review_gtk3.py crashed with SIGSEGV in g_main_context_dispatch()

[Rafał Grykałowski]

I was trying to add comment to software - XBMC, and i saw bug.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: software-center 5.3.13
ProcVersionSignature: Ubuntu 3.5.0-14.18-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Fri Sep 14 21:42:48 2012
ExecutablePath: /usr/share/software-center/submit_review_gtk3.py
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120913)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/software-center/submit_review_gtk3.py --pkgname xbmc --iconname xbmc --parent-xid --version 2:11.0~git20120510.82388d5-1ubuntu1 --origin ubuntu --datadir /usr/share/software-center/ --appname XBMC\ Media\ Center
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80a2f9d: addl $0x1,0x54(%ebp)
 PC (0x080a2f9d) ok
 source "$0x1" ok
 destination "0x54(%ebp)" (0x00000054) 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/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: submit_review_gtk3.py 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 #1048886, 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.