luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-23 18:52:09 +01:00
Code Issues Packages Projects Releases Wiki Activity

GDBus: Don't log a message for G_DBUS_CONNECTION_FLAGS_CROSS_NAMESPACE

Browse Source 
This was intended to make it feasible to debug connection failures where
a modern GDBus client connects to a GDBusServer that is missing
glib!2826, but those GDBusServers should be increasingly rare: we have
had the fixed version of GDBusServer for 5 GNOME stable releases
(2 years), long enough to get into stable releases of Debian and Ubuntu
and a service-pack release of SUSE.

This debug message can be very noisy, especially when unit-testing
GLib code (which is frequently done with G_MESSAGES_DEBUG=all) or when
a third-party GLogFunc ignores the log_level parameter and logs all
messages as though they indicated a serious problem. I think it has
served its purpose now.

Signed-off-by: Simon McVittie <smcv@collabora.com>
This commit is contained in:
Simon McVittie 2024-09-18 14:02:46 +01:00
parent f1140eceb7
commit cb185c22bc
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
gio/gdbusauthmechanismexternal.c
View File

@ -382,7 +382,6 @@ mechanism_client_initiate (GDBusAuthMechanism *mechanism,
* no way to express an empty authorization identity this way. * no way to express an empty authorization identity this way.
* Instead, we'll reply to the server's first (empty) challenge * Instead, we'll reply to the server's first (empty) challenge
* with an empty authorization identity in our first response. */ * with an empty authorization identity in our first response. */
g_debug ("Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)");
} }
else else
{ {