luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-09-20 01:06:15 +02:00
Code Issues Packages Projects Releases Wiki Activity

GSettings tool: work-around GDBus issue

Browse Source 
There is currently no way (near as I can tell) to ensure that a message
has been sent when using GDBus.  If we exit() before we are sure, then
it is very possible that the message isn't sent at all.  This behaviour
was observed when using the GSettings commandline tool with dconf.

A quick and dirty workaround for now.
This commit is contained in:
Ryan Lortie 2010-05-16 13:03:34 +02:00
parent 8e060adb2c
commit 849684e540
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
gio/gsettings-tool.c
View File

@ -215,6 +215,24 @@ handle_set (gint *argc,
ret = 0;
/* XXX: workaround for now
*
* if we exit() so quickly, GDBus may not have had a chance to
* actually send the message (since we're using it async).
*
* GDBusConnection has no API to sync or wait for messages to be sent,
* so we send a meaningless message and wait for the reply to ensure
* that all messages that came before must have been sent.
*/
{
GDBusConnection *session;
session = g_bus_get_sync (G_BUS_TYPE_SESSION, NULL, NULL);
g_dbus_connection_call_sync (session, "org.gtk.DoesNotExist", "/",
"org.gtk.DoesNotExist", "Workaround",
g_variant_new ("()"), 0, -1, NULL, NULL);
}
out:
g_option_context_free (context);