[Bug 48196] New: No information on why tubes close

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=48196

             Bug #: 48196
           Summary: No information on why tubes close
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


Currently, if you have a tube you don't want, the only way to get rid of it is
to Close() it. Equally, if a tube closes up for some reason, the only way the
CM can report it is by emitting Closed. There's no API for explicitly rejecting
an offered tube, or for propagating errors.

>From test_offer_invalidated_before_open in tests/dbus/dbus-tube.c in tp-glib:

  /* FIXME: this isn't a particularly good error… it's just what comes out when
   * the channel gets closed from under us, and there isn't really API on
   * DBusTube to give a better error.
   */
  g_assert_error (test->error, TP_DBUS_ERRORS, TP_DBUS_ERROR_OBJECT_REMOVED);

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.