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

[Arne Meyer]

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
software-center:
  Installiert: 13.08-0ubuntu1
  Installationskandidat: 13.08-0ubuntu1
  Versionstabelle:
 *** 13.08-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

After right-click a .deb package (teamviewer_linux_x64.deb) to install it with software-manager,
the software-manager pops up and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.08-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 8 15:58:28 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2011-10-06 (672 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with UnicodeDecodeError in parse_applications_menu(): 'ascii' codec can't decode byte 0xc3 in position 5: ordinal not in range(128)
UpgradeStatus: Upgraded to saucy on 2013-06-18 (51 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Arne Meyer (am-v)]

usind dpkg -i teamviewer_linux_x64.deb starts to install but can't solve dependencies (libasound2 and ia32-libs) so no crash on dpkg

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