mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-02-15 06:47:14 +01:00
f773bd8b76
This can easily happen if the owner of the remote object vanishes. Of course, when that happens, user code is already notified (by e.g. the notify::g-name-owner signal) so it can avoid using the proxy but requiring that is a bit harsh. IOW, before this patch this critical error was printed GLib-GIO-CRITICAL **: g_dbus_gvariant_to_gvalue: assertion `value != NULL' failed when that happened. With this patch, we just avoid setting the GValue so the user will get the default value for its type instead. So, for example, if the user code is getting a GVariant property on such a defunct proxy, then he gets a NULL back. So unless said user code checks the return value, criticals will still be printed if the NULL GVariant is used for anything interesting. Signed-off-by: David Zeuthen <davidz@redhat.com>