apport-retrace crashed with UnicodeEncodeError in exit() when scanning a CoreDump directly

[Thorsten Sick]

Binary package hint: apport

I just did a
"apport-retrace CoreDump"
to find out if there will be any useful result. Well. It crashes.
Seems not to be handling wrong file formats in a proper way.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: apport-retrace 1.13.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
CrashReports:
 600:1000:1000:9761:2010-08-21 21:41:23.627380000 +0200:2010-08-21 21:41:26.786484711 +0200:/var/crash/_usr_bin_apport-retrace.1000.crash
 600:1000:1000:17755567:2010-08-20 17:03:48.591726000 +0200:2010-08-20 17:03:52.291724129 +0200:/var/crash/_usr_lib_nspluginwrapper_i386_linux_npviewer.bin.1000.crash
 600:1000:1000:33962745:2010-08-19 10:22:04.564491000 +0200:2010-08-19 10:22:06.394495526 +0200:/var/crash/_usr_games_warzone2100.1000.crash
 600:1000:1000:11072447:2010-08-21 19:27:26.155828000 +0200:2010-08-21 19:27:29.626135460 +0200:/var/crash/_usr_bin_anjuta.1000.crash
Date: Sat Aug 21 21:41:24 2010
ExecutablePath: /usr/bin/apport-retrace
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/apport-retrace CoreDump
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.utf8
PythonArgs: ['/usr/bin/apport-retrace', 'CoreDump']
SourcePackage: apport
Title: apport-retrace crashed with UnicodeEncodeError in exit()
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 #448158, 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.