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 673372 - GDBusServer does not stop listening if you destroy it without calling _start()
GDBusServer does not stop listening if you destroy it without calling _start()
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other Linux
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2012-04-02 15:09 UTC by Will Thompson
Modified: 2018-05-24 13:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A little application demonstrating the problem. (1.30 KB, text/x-csrc)
2012-04-02 15:09 UTC, Will Thompson 		Details

Description Will Thompson 2012-04-02 15:09:27 UTC 
Created attachment 211139 [details]
A little application demonstrating the problem.

If you create a GDBusServer with g_dbus_server_new_sync(), but never call g_dbus_server_start(), calling g_dbus_server_stop() and then unreffing it apparently does not stop it listening on the socket. Subsequent attempts to create a GDBusServer for the same address fail with “Error binding to address: Address already in use (g-io-error-quark, 33)”.

Calling g_dbus_server_start() immediately before calling g_dbus_server_stop() and unreffing it makes it clean up after itself properly.
Comment 1 GNOME Infrastructure Team 2018-05-24 13:56:50 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/530.