Bug 25487

Summary: [abrt] crash detected in telepathy-butterfly-0.5.3-1.fc12
Product: Telepathy Reporter: Brian Pepple <bpepple>
Component: butterflyAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED WORKSFORME QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Brian Pepple 2009-12-07 07:56:43 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Connect to an MSN account
2. Connect on a different machine. You will be disconnected.
3. Press "Edit account", and unmark and mark "Enabled". Then apply

Comment: Happened when I reconnected to MSN after logging in on a different
computer

backtrace
-----
Summary: TBb91a46a5 connection.py:332:on_oim_messages_fetched:AttributeError:
'NoneType' object has no attribute 'account'

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/papyon/client.py", line 471, in event
    self._dispatch(method_name, *args[:-1])
  File "/usr/lib/python2.6/site-packages/papyon/event/__init__.py", line 44, in
_dispatch
    if event_handler._dispatch_event(name, *args):
  File "/usr/lib/python2.6/site-packages/papyon/event/__init__.py", line 65, in
_dispatch_event
    handler(*params)
  File "/usr/lib/python2.6/site-packages/butterfly/connection.py", line 332, in
on_oim_messages_fetched
    logger.info('received offline message from %s : %s' % (sender.account,
message.text))
AttributeError: 'NoneType' object has no attribute 'account'

Local variables in innermost frame:
handle: <butterfly.handle.ButterflyContactHandle object at 0x949156c>
sender: None
self: <butterfly.connection.ButterflyConnection at
/org/freedesktop/Telepathy/Connection/butterfly/msn/fiedler_40daimi_2eau_2edk
at 0x92e3e8c>
messages: [<OfflineMessage run_id= seq_num=-1>, <OfflineMessage run_id=
seq_num=-1>, <OfflineMessage run_id=5BC43943-8943-5549-7046-7BB43655A685
seq_num=2>]
props: {'org.freedesktop.Telepathy.Channel.TargetHandleType': 1,
'org.freedesktop.Telepathy.Channel.ChannelType':
'org.freedesktop.Telepathy.Channel.Type.Text',
'org.freedesktop.Telepathy.Channel.Requested': False,
'org.freedesktop.Telepathy.Channel.TargetHandle': 9}
message: Tror det er fikset nu
channel: <butterfly.channel.text.ButterflyTextChannel at
/org/freedesktop/Telepathy/Connection/butterfly/msn/fiedler_40daimi_2eau_2edk/channel7
at 0x94919cc>

cmdline: /usr/bin/python /usr/libexec/telepathy-butterfly 
component: telepathy-butterfly
executable: /usr/libexec/telepathy-butterfly
kernel: 2.6.31.6-145.fc12.i686
package: telepathy-butterfly-0.5.3-1.fc12
uuid: b91a46a5
Comment 1 Jonny Lamb 2010-03-15 10:41:34 UTC
This bug isn't because you signed in on another machine. That works fine in butterfly. Something went wrong in receiving an offline message.

This is suspicious:

messages: [<OfflineMessage run_id= seq_num=-1>, <OfflineMessage run_id=
seq_num=-1>, <OfflineMessage run_id=5BC43943-8943-5549-7046-7BB43655A685
seq_num=2>]

I think this might be a papyon bug. It shouldn't be giving us broken offline messages.

Could you get a full butterfly log please? Exit Empathy, wait five seconds, and call:

BUTTERFLY_LOGFILE=butterflylog BUTTERFLY_PERSIST=1 /usr/libexec/telepathy-butterfly

Then connect in Empathy and when it crashes, logout and attach the log to this bug. If you are scared of all your contacts being visible in this log, then you can email it to me at jonny.lamb@collabora.co.uk , but it would be nicer if you could just attach it here.
Comment 2 Kåre Fiedler Christiansen 2010-11-07 05:27:45 UTC
This bug was reported up stream by the package maintainer of empathy based on a bug report in the fedora bugtracker from me. Unfortunately, I wasn't aware of that at the time, so I haven't provided the requested feedback.

By now my system has been updated, and I cannot reproduce the bug. My apologies.

I'm taking the liberty of closing this bug, since no further data can be provided.

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.