GNOME Bugzilla – Bug 688370
GDBusError documentation improvement for client-side
Last modified: 2012-11-15 21:25:53 UTC
The GDBusError section documentation says: "With this setup, a D-Bus peer can transparently pass e.g. FOO_BAR_ERROR_ANOTHER_ERROR and other peers will see the D-Bus error name org.project.Foo.Bar.Error.AnotherError. If the other peer is using GDBus, the peer will see also FOO_BAR_ERROR_ANOTHER_ERROR instead of G_IO_ERROR_DBUS_ERROR. Note that GDBus clients can still recover org.project.Foo.Bar.Error.AnotherError using g_dbus_error_get_remote_error()." But the truth is that having the peer using GDBus is not enough to get the DBus error name to GError conversion right: the client needs to explicitly register the error domain itself before attempting any DBus call. Which is actually obvious, but worth explicitly noting...
Created attachment 229026 [details] [review] Suggested rewording
Comment on attachment 229026 [details] [review] Suggested rewording Sounds good to me, thanks!
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.