telepathy-butterfly crashed with KeyError in disconnected(): <butterfly.connection.ButterflyConnection at /org/freedesktop/Telepathy/Connection/butterfly/msn/vitorsouza_40msn_2ecom at 0xb699070c>
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-butterfly (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: telepathy-butterfly
From time to time I've been getting and ignoring this message. I decided to report it now because it happened so many times, but I'm almost sure that it has to do with the network settings of my workplace. I think MSN ports are blocked here and maybe that's why the error happens. Still, maybe with the information collected from apport someone discovers some kind of bug there.
vitor@seattle:~$ lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
vitor@seattle:~$ apt-cache policy telepathy-butterfly
telepathy-
Installed: 0.5.15-1
Candidate: 0.5.15-1
Version table:
*** 0.5.15-1 0
500 http://
100 /var/lib/
The error dialog comes out of nowhere. I had started Empathy a while ago and it's still running OK, just no MSN.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-butterfly 0.5.15-1
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
Date: Thu Apr 7 09:02:46 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=en_US:en
LANG=en_US.UTF-8
PythonArgs: ['/usr/
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with KeyError in disconnected(): <butterfly.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.