commit b8aad73af9325307a9cf82544a38d58480bd6ebb
Author: Matthias Clasen <[email protected]>
Date:   Wed Aug 19 16:24:22 2015 -0400

   2.45.6

NEWS         | 5 +++++
configure.ac | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)

commit 8d8a1c205b8eb5b54ea1fc8a2e39197dacb1788b
Author: Dan Winship <[email protected]>
Date:   Wed Aug 19 16:21:46 2015 -0400

   fix previous

gio/gdbusmethodinvocation.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

commit c6862451411ae3039029fdd1e3697343fa2aed19
Author: Dan Winship <[email protected]>
Date:   Wed Aug 19 13:21:00 2015 -0400

   gdbus: don't warn when returning a value on a closed connection

   g_dbus_method_invocation_return_value(), etc, don't have GError
   parameters (which makes sense since they won't usually return errors,
   and there's not much you could do if they did), so in the rare case
   when something does go wrong, they print a warning.

   However, there is at least one situation where the warning is a bad
   idea: if you are using private bus connections, and a client connects,
   makes a request, and then disconnects before getting the response.
   Given that there's nothing the caller can do to prevent this case from
   getting hit (since the client might not disconnect until after the
   call to g_dbus_method_invocation_return_value() starts) and given that
   the server can never actually know for sure that the client has
   received the response (it might disconnect after reading the response,
   but before processing it), just kill the warning in this case.

   https://bugzilla.gnome.org/show_bug.cgi?id=753839

gio/gdbusmethodinvocation.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.