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 648959 - Allow setting :connection property GDBusObjectManagerServer
Allow setting :connection property GDBusObjectManagerServer
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other Linux
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-04-29 17:30 UTC by David Zeuthen (not reading bugmail)
Modified: 2011-05-04 07:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Zeuthen (not reading bugmail) 2011-04-29 17:30:03 UTC 
As per bug 647577 comment 11. We should also allow it being NULL. And the docs should mention why you would want to do this: to prime the server before it is exported on :connection - otherwise a lot of useless signals are generated at startup.
Comment 1 Simon McVittie 2011-05-01 20:29:54 UTC 
Also when you want your object to vanish from D-Bus deterministically, when it's "conceptually already gone" but something asynchronous might still be holding a ref to it. (In Telepathy we used to rely on dbus-glib's implicit removal from D-Bus as a side-effect of the last unref, but that led to some really odd bugs.)
Comment 2 David Zeuthen (not reading bugmail) 2011-05-04 07:49:15 UTC 
OK, fixed with this commit

 http://git.gnome.org/browse/glib/commit/?id=1ab29b6c4a2ddf5a60b4cc353422d605197b7696