Bug 28233

Summary: [0.5.10] telepathy-butterfly crashed with NameError in parse()
Product: Telepathy Reporter: Cristian Aravena <caravena>
Component: butterflyAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED DUPLICATE QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: _usr_lib_telepathy_telepathy-butterfly.1000.crash
_usr_lib_telepathy_telepathy-butterfly.1000.crash
butterfly.log

Description Cristian Aravena 2010-05-24 09:15:32 UTC
Created attachment 35825 [details]
_usr_lib_telepathy_telepathy-butterfly.1000.crash

ProblemType: Crash
Date: Mon May 24 12:12:58 2010
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_CL.utf8


PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/papyon/msnp/base.py", line 107, in _dispatch_command
     handler(command)
   File "/usr/lib/pymodules/python2.6/papyon/msnp/notification.py", line 453, in _handle_NLN
     urllib.unquote(command.arguments[idx]))
   File "/usr/lib/pymodules/python2.6/papyon/p2p.py", line 183, in parse
     shad = __decode_shad(shad)
 NameError: global name '_MSNObject__decode_shad' is not defined
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Comment 1 Cristian Aravena 2010-05-24 09:18:38 UTC
telepathy-butterfly 0.5.10-1~ppa10.04+1
Comment 2 Cristian Aravena 2010-05-24 10:20:37 UTC
Created attachment 35827 [details]
_usr_lib_telepathy_telepathy-butterfly.1000.crash
Comment 3 Cristian Aravena 2010-05-24 14:52:13 UTC
Created attachment 35837 [details]
butterfly.log
Comment 4 Jonny Lamb 2010-05-29 07:50:45 UTC

*** This bug has been marked as a duplicate of bug 28278 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.