Warning in galago-telepathy-feed (output of galago-daemon)

[Nicolas DERIVE]

Binary package hint: galago-telepathy-feed

A warning was emitted (during a butterfly connexion in telepathy) by the galago-daemon (that I launched in a terminal) :

(process:13749): telepathy-feed-WARNING **: Cannot get name for handle: Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/service.py", line 451, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.5/site-packages/telepathy/server/conn.py", line 233, in InspectHandles
    self.check_handle(handle_type, handle)
  File "/usr/lib/python2.5/site-packages/telepathy/server/conn.py", line 150, in check_handle
    (handle, handle_type))
InvalidHandle: handle number 77 not valid for type 1

(process:13749): telepathy-feed-WARNING **: Cannot get name for handle: Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/service.py", line 451, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.5/site-packages/telepathy/server/conn.py", line 233, in InspectHandles
    self.check_handle(handle_type, handle)
  File "/usr/lib/python2.5/site-packages/telepathy/server/conn.py", line 150, in check_handle
    (handle, handle_type))
InvalidHandle: handle number 78 not valid for type 1

[Daniel Holbach (dholbach)]

Thanks for your bug report. Looks like a telepathy-python bug.

[Daniel Holbach (dholbach)]

Somebody of the team should forward it upstream.

[Nicolas-derive (nicolas-derive)]

A warning was emitted (during a butterfly connexion in telepathy) by the galago-daemon (that I launched in a terminal), see the Launchpad bug report https://bugs.launchpad.net/telepathy-python/+bug/106167/ for further details.

[Nicolas DERIVE (kalon33)]

Linked to the upstream bug report at freedesktop bugzilla.

[Simon McVittie (smcv)]

Don't be so sure that this is a telepathy-python bug - if a Telepathy client inspects any invalid handle (e.g. some random number that isn't actually a handle, or a handle that's expired and gone out of scope), an exception will occur, with traceback similar to the one above. This is by design.

[Simon McVittie (smcv)]

Is this reproducible, and can you get any further debug logs? It's likely to have been a bug in either butterfly or telepathy-feed rather than in telepathy-python - telepathy-feed is inspecting handles that butterfly has, for whatever reason, invalidated (e.g. because the contact disappeared, or because for some reason butterfly gave telepathy-feed some invalid handles in response to an earlier call).

As I commented on the Launchpad bug, the traceback is to be expected in this situation and does not indicate a bug in telepathy-python.

[Benjamin-close (benjamin-close)]

Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler

[Jonny-lamb (jonny-lamb)]

WORKSFORME

Feel free to re-open if you have more information.