telepathy-butterfly crashed with TypeError in __parse_metadata()

[Nathan Rogers]

Binary package hint: telepathy-butterfly

- Ubuntu Karmic Alpha 5 with all recent updates (9/12/09)
- this error occurred when trying to add a yahoo account after the initial start of Empathy 2.27.92
  empathy:
  Installed: 2.27.92-1ubuntu1
  Candidate: 2.27.92-1ubuntu1
  Version table:
 *** 2.27.92-1ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

  telepathy-butterfly:
  Installed: 0.5.0-0ubuntu2
  Candidate: 0.5.0-0ubuntu2
  Version table:
 *** 0.5.0-0ubuntu2 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

- I initially added a Hotmail account, which was successful, I then wanted to add a yahoo account which failed with a crash. Subsequent attempts at adding a yahoo account have been unsuccessful. When a Yahoo account-type is selected, non of the entry fields or labels are drawn (see attached screen shot).

ProblemType: Crash
Architecture: i386
Date: Sat Sep 12 11:09:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: telepathy-butterfly 0.5.0-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with TypeError in __parse_metadata()
Uname: Linux 2.6.31-10-generic i686
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 #426351, 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.