Bug 28884

Summary: [Muji] Telepathy-butterfly crash
Product: Telepathy Reporter: Yann <yannubuntu>
Component: generalAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Yann 2010-07-01 22:38:46 UTC
(was first reported here : https://bugzilla.gnome.org/show_bug.cgi?id=622946 )

On ubuntu 10.04, EmpathyPPA, Muji

when trying to connect ubuntu-fr@conference.luon.net room with my gmail adress,
2nd Muji window opens but Apport opens a "telepathy-butterfly crash" window
(that leads to nothing as "it is a genuine package") and terminal gives the
following log:

$ VIDEO_DEVICE=/dev/video0 python new-call-demo/callui.py
* starting audio call
Showing window
FAILURE: org.freedesktop.Telepathy.Error.Disconnected (Channel aborted)


then when I close Muji:
Traceback (most recent call last):
File "/home/yyy/new-call-demo/callchannelui.py", line 102 in <lambda>
lambda x: self.channel.hangup(
AttributeError: 'CallChannelUI' object has no attribute 'channel' 
Traceback (most recent call last):
  File "/home/yyy/new-call-demo/callchannelui.py", line 321, in window_closed
    self.channel.hangup(CALL_STATE_CHANGE_REASON_REQUESTED,
AttributeError: 'CallChannelUI' object has no attribute 'channel'


I then just closed Muji, and restarted empathy. I got the same
Telepathy-butterfly (this problem can not be reported. This is not a genuine
Ubuntu package).

So maybe the crash is not linked to Muji...
Comment 1 GitLab Migration User 2019-12-09 11:21:51 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/158.

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.