telepathy-butterfly crashed with UnicodeDecodeError in _print_MSG()

Bug #438600 reported by João Pinto
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
telepathy-butterfly (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: telepathy-butterfly

I have imported the contats from pidgin, empathy just crashed after enabling the accounts.

ProblemType: Crash
Architecture: i386
Date: Tue Sep 29 09:31:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InterpreterPath: /usr/bin/python2.6
Package: telepathy-butterfly 0.5.0-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=pt_PT.utf8
 LANG=pt_PT.utf8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with UnicodeDecodeError in _print_MSG()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
João Pinto (joaopinto) wrote :
Revision history for this message
João Pinto (joaopinto) wrote :

Upgrade to 0.5.1-1~ppa9.10+1 as recommended on #telepathy .
The problem is still happening.

João Pinto (joaopinto)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #432558, 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.

tags: removed: need-duplicate-check
Revision history for this message
João Pinto (joaopinto) wrote :

The bug linked by the retracing is not accessible to me. I am unable to check if the bug is really a duplicate so I am keeping this bug open.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.