[Telepathy] [Bug 15325] New: Extensions for an interface conflict with tp-glib implementation of the same interface

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=15325

           Summary: Extensions for an interface conflict with tp-glib
                    implementation of the same interface
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: high
         Component: telepathy-glib
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk


If a project has an internal implementation of an interface (e.g. Hold), and
telepathy-glib adds an implementation of the same interface, they will fight -
specifically, they will try to add the same dbus-glib signals for the same
DBusGProxy, causing an assertion failure.

We should fix this before releasing telepathy-glib with Hold (version 0.7.6),
so setting as a blocker.

Desired functionality: suppose telepathy-glib and some project-specific
extensions both implement the Hold interface. Then the project-specific
extensions should be assumed to be right, and tp-glib's signal-adding should
not happen.

My branch of telepathy-inspector can be used to reproduce this, if compiled
against my tp-glib-smcv branch. The symptom is:

** (telepathy-inspector:22914): CRITICAL **: dbus_g_proxy_add_signal: assertion
`g_datalist_id_get_data (&priv->signal_signatures, q) == NULL' failed


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