software-center-gtk3 crashed with UnicodeDecodeError in get_suggestions(): 'ascii' codec can't decode byte 0xc3 in position 57: ordinal not in range(128)

[J]

none

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-center 4.1.21
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic-pae 3.0.4
Uname: Linux 3.0.0-10-generic-pae i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Fri Sep 9 09:57:47 2011
ExecutablePath: /usr/share/software-center/software-center-gtk3
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center-gtk3
PythonArgs: ['/usr/bin/software-center-gtk3']
SoftwareCenterLog:
 2011-09-09 09:56:55,101 - softwarecenter.ui.gtk3.em - INFO - EM's: 15 12 17
 2011-09-09 09:56:56,396 - softwarecenter.fixme - WARNING - logs to the root logger: '('/usr/share/software-center/softwarecenter/db/database.py', 175, 'open')'
 2011-09-09 09:56:56,395 - root - WARNING - failed to add sca db Couldn't stat '/home/phoenix/.cache/software-center/software-center-agent.db' (No existe el archivo o el directorio)
 2011-09-09 09:56:56,968 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file
 2011-09-09 09:57:02,102 - softwarecenter.ui.gtk3.app - INFO - software-center-agent finished with status 1
SourcePackage: software-center
Title: software-center-gtk3 crashed with UnicodeDecodeError in get_suggestions(): 'ascii' codec can't decode byte 0xc3 in position 57: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #843195, 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.