telepathy-butterfly crashed with InvalidArgument in _get_initial_channels()

Bug #550553 reported by Felipe Bernardo Zorzo
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
telepathy-butterfly
Unknown
Medium
telepathy-butterfly (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: telepathy-butterfly

I was using Ubuntu 10.04 beta 1 (with all updates) when telepathy-butterfly crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-butterfly 0.5.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sun Mar 28 19:50:33 2010
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.utf8
PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly']
SourcePackage: telepathy-butterfly
Title: telepathy-butterfly crashed with InvalidArgument in _get_initial_channels()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Felipe Bernardo Zorzo (felipe-b-zorzo) wrote :
tags: removed: need-duplicate-check
Revision history for this message
In , Sebastien Bacher (seb128) wrote :

The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly/+bug/550553

"I was using Ubuntu 10.04 beta 1 (with all updates) when telepathy-butterfly crashed.

telepathy-butterfly 0.5.7-0ubuntu1

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/papyon/switchboard_manager.py", line 75, in <lambda>
    lambda sb, contact: self.__on_user_joined(contact))
  File "/usr/lib/pymodules/python2.6/papyon/switchboard_manager.py", line 136, in __on_user_joined
    self._on_contact_joined(contact)
  File "/usr/lib/pymodules/python2.6/papyon/conversation.py", line 335, in _on_contact_joined
    self._dispatch("on_conversation_user_joined", contact)
  File "/usr/lib/pymodules/python2.6/papyon/event/__init__.py", line 44, in _dispatch
    if event_handler._dispatch_event(name, *args):
  File "/usr/lib/pymodules/python2.6/papyon/event/__init__.py", line 65, in _dispatch_event
    handler(*params)
  File "/usr/lib/python2.6/dist-packages/butterfly/channel/im.py", line 151, in on_conversation_user_joined
    signal=True, conversation=None)
  File "/usr/lib/python2.6/dist-packages/telepathy/server/channelmanager.py", line 120, in channel_for_props
    return self.create_channel_for_props(props, signal, **args)
  File "/usr/lib/python2.6/dist-packages/telepathy/server/channelmanager.py", line 105, in create_channel_for_props
    props, **args)
  File "/usr/lib/python2.6/dist-packages/butterfly/channel_manager.py", line 157, in _get_text_channel
    object_path=path)
  File "/usr/lib/python2.6/dist-packages/butterfly/channel/conference.py", line 46, in __init__
    ic = self._get_initial_channels(props)
  File "/usr/lib/python2.6/dist-packages/butterfly/channel/conference.py", line 104, in _get_initial_channels
    raise telepathy.InvalidArgument("Couldn't find any channels referred to in InitialChannels")
InvalidArgument: org.freedesktop.Telepathy.Error.InvalidArgument: Couldn't find any channels referred to in InitialChannels"

Revision history for this message
In , Jonny-lamb (jonny-lamb) wrote :

What's happening here is the user is having a 1-1 chat with contact A, then contact A is inviting contact B to the chat. The 1-1 channel gets the on_conversation_user_joined callback as it should, then tries to create a new conference MUC channel for the three to chat in.

The 1-1 chat should pass its object path as the contents of InitialChannels so the conference channel will take off where the 1-1 channel started, but the conference channel is complaining that it can't find the Channel object in the connection to steal its switchboard.

This is odd. I just tried to replicate it by having contacts A and B using pidgin and the user using butterfly but couldn't?

Could you ask the launchpad bug submitter to provide logs of it happening again please? Very odd.

visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugs.freedesktop.org/show_bug.cgi?id=27560

Changed in telepathy-butterfly (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you know how to trigger the issue? Could you get the butterfly log in the empathy debug dialog when getting the issue?

Changed in telepathy-butterfly (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in telepathy-butterfly (Ubuntu):
status: Incomplete → Invalid
Changed in telepathy-butterfly:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in telepathy-butterfly:
importance: Medium → Unknown
Changed in telepathy-butterfly:
importance: Unknown → Medium
Revision history for this message
In , Gitlab-migration (gitlab-migration) wrote :

-- 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-butterfly/issues/15.

Changed in telepathy-butterfly:
status: Confirmed → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.