Apport reported that telepathy-butterfly crashed with UnicodeDecodeError

[alfabravoteam]

Binary package hint: telepathy-butterfly

Was logging in to the accounts (multiple gtalk accounts, one Msn, one yahoo), apport raised the message indicating that the process died. No further information available.

alfabravo@alfabravoTiger:~$ uname -a
Linux alfabravoTiger 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

alfabravo@alfabravoTiger:~$ sudo apt-cache policy telepathy-butterfly
[sudo] password for alfabravo:
telepathy-butterfly:
  Installed: 0.5.15-1
  Candidate: 0.5.15-1
  Version table:
 *** 0.5.15-1 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-butterfly 0.5.15-1
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: efa7a38a6e953d2e9f0428c501fc834f
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Thu Jun 9 15:42:59 2011
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with UnicodeDecodeError in _signal_text_received(): 'ascii' codec can't decode byte 0xc3 in position 18: ordinal not in range(128)
UpgradeStatus: Upgraded to natty on 2011-04-11 (59 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare vboxusers www-data

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