After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757945 - gdbus: fix unexporting interface skeleton when resetting GDBusObjectManager's connection
gdbus: fix unexporting interface skeleton when resetting GDBusObjectManager's...
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-11-11 13:51 UTC by Thomas Haller
Modified: 2018-05-24 18:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdbus: fix unexporting interface skeleton when resetting GDBusObjectManager's connection (3.09 KB, patch)
2015-11-11 13:51 UTC, Thomas Haller 		none Details | Review

Description Thomas Haller 2015-11-11 13:51:06 UTC 
A single interface skelton can be exported via different
    GDBusObjectManagers. However, resetting the connection
    of one object-manager would unexport its skeleton from all
    connections.

    This bug effectively makes it impossible to export the same skelton
    on multiple object-manager.
Comment 1 Thomas Haller 2015-11-11 13:51:10 UTC 
Created attachment 315263 [details] [review]
gdbus: fix unexporting interface skeleton when resetting GDBusObjectManager's connection

A single interface skelton can be exported via different
GDBusObjectManagers. However, resetting the connection
of one object-manager would unexport its skeleton from all
connections.

This bug effectively makes it impossible to export the same skelton
on multiple object-manager.
Comment 2 GNOME Infrastructure Team 2018-05-24 18:19:47 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME'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.gnome.org/GNOME/glib/issues/1102.