software-center crashed with Exception in get_reviews(): failed to launch: '['/usr/share/software-center/get_reviews_helper.py', '--language', 'en', '--origin', 'ubuntu', '--distroseries', 'natty', '--pkgname', u'gsoko']' (error: 'glib.spawn_async: first argument must be a sequence of strings')

[Niklas Bolmdahl]

Binary package hint: software-center

I clicked an install-suggestion icon from Unity while I had the software center already open. This was followed by multiple crash-dialogs, although both installs seem to have gone through just fine. (one was underway in the previously opened window, and I initiated another one in the newly opened window)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.26.4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sat Apr 16 19:36:43 2011
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en
 LANG=sv_SE.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with Exception in get_reviews(): failed to launch: '['/usr/share/software-center/get_reviews_helper.py', '--language', 'en', '--origin', 'ubuntu', '--distroseries', 'natty', '--pkgname', u'gsoko']' (error: 'glib.spawn_async: first argument must be a sequence of strings')
UpgradeStatus: Upgraded to natty on 2011-04-07 (8 days ago)
UserGroups: adm admin cdrom dialout floppy lpadmin nopasswdlogin plugdev sambashare tape

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #761922, 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.