telepathy-butterfly crashed with KeyError in disconnected(): <butterfly.connection.ButterflyConnection at /org/freedesktop/Telepathy/Connection/butterfly/

[DavidW617]

Binary package hint: telepathy-butterfly

Description: Ubuntu Natty (development branch)
Release: 11.04

telepathy-butterfly:
  Installed: 0.5.15-1
  Candidate: 0.5.15-1
  Version table:
 *** 0.5.15-1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

This bug occurred after my computer was restored from sleep state before the internet connected.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-butterfly 0.5.15-1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 4f5564c50a42755fd0a913a86e07ee6a
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Thu Mar 31 14:17:55 2011
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_CA.UTF-8
 PATH=(custom, user)
 LANGUAGE=en_CA:en
 LANG=en_HK.utf8
PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with KeyError in disconnected(): <butterfly.connection.ButterflyConnection at /org/freedesktop/Telepathy/Connection/butterfly/msn/ashaman_5fdavid_40hotmail_2ecom at 0x891b86c>
UpgradeStatus: Upgraded to natty on 2011-03-13 (18 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin mythtv netdev 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 #722897, 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.