| Summary: | telepathy-butterfly crashed with NotImplementedError in _on_error() | ||
|---|---|---|---|
| Product: | papyon | Reporter: | Kjell Braden <fnord> |
| Component: | general | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED NOTABUG | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | critical | ||
| Priority: | medium | CC: | bpepple, caravena, om26er, sense, teemu.heinamaki |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | http://git.collabora.co.uk/?p=user/jonny/papyon.git;a=shortlog;h=refs/heads/p2p-switchboard-error | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
crash log
patch |
||
|
Description
Kjell Braden
2008-08-01 06:02:35 UTC
Bug still present with pymsn 0.3.3 Strangely this method is defined in AbstractConversation and following the MRO should be called but it's the function defined in SwitchboardClient that get called instead and raise the exception. Any idea? *** Bug 24308 has been marked as a duplicate of this bug. *** 14 duplicated in Ubuntu whenever I get a message from msn telepathy butterfly crashes (In reply to comment #5) > whenever I get a message from msn telepathy butterfly crashes Please could you post some butterfly logs? If you don't want information about your contacts to be publicly available online, feel free to email me the logs privately: jonny.lamb@collabora.co.uk Created attachment 34017 [details]
crash log
Here is a log where this crash happens. The interesting part is near the end.
Created attachment 34031 [details]
patch
I added myself to my contact list and couldn't reproduce this.
I did, however, find another bug in butterfly, so that's nice. :-)
So, I was just looking at the code and it just appears as if we're getting the "NAK" command, which immediately emits the message-undelivered signal in the NAK handler, and SwitchboardClient just has a dummy NotImplementedError stub as the callback.
However, I am a little confused as to what switchboard client this is actually appearing on, as SwitchboardClient is never used directly. I'm going to guess it's SwitchboardP2PTransport, as that's the only subclass that doesn't define an _on_error method.
If you know how to use pdb, could you break when it calls _on_error (and then raises the exception) and find out exactly what object self is? Otherwise, attach a log using papyon from git master with the attached patch applied.
Another thing: is this actually a bug, or are you just saying "I got a traceback"? By the looks of it, nothing bad is happening as a result of this? Perhaps apport is screaming in your face, but is there anything actually going wrong with butterfly?
Someone in the Ubuntu bug report provided an error log as well at <http://launchpadlibrarian.net/40927602/butterfly>. The bug seems to be pretty easy to reproduce in Ubuntu Lucid, the crash appears at least a few times if Empathy is running. (In reply to comment #9) > Someone in the Ubuntu bug report provided an error log as well at > <http://launchpadlibrarian.net/40927602/butterfly>. This is a completely unrelated bug and has already been fixed. On a more related note, I've got a branch to "fix" this bug. Check it out. (In reply to comment #10) > (In reply to comment #9) > > Someone in the Ubuntu bug report provided an error log as well at > > <http://launchpadlibrarian.net/40927602/butterfly>. > > This is a completely unrelated bug and has already been fixed. > > On a more related note, I've got a branch to "fix" this bug. Check it out. This just hide the bug to make apport happy, is there really a point to merge it upstream? (In reply to comment #11) > This just hide the bug to make apport happy, is there really a point to merge > it upstream? I didn't realise until recently that apport is told to be quiet in actual Ubuntu releases, so let's ignore this one. NOTABUG *** Bug 28190 has been marked as a duplicate of this bug. *** *** Bug 28593 has been marked as a duplicate of this bug. *** |
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.