Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I don't see the reason for this warning.
Looking at g_dbus_method_invocation_return_value_internal() in glib/gio/gdbusmethodinvocation.c:
error = NULL;
if (!g_dbus_connection_send_message (g_dbus_method_invocation_get_connection (invocation), reply, G_DBUS_SEND_MESSAGE_FLAGS_NONE, NULL, &error))
{
g_warning ("Error sending message: %s", error->message);
g_error_free (error);
}
Seems like a glib bug to me.
CC-ing danw
I guess the assumption is that errors shouldn't normally occur there, and if they do, there's not really anything the caller could do about it, so it doesn't make sense to return a GError to the caller, but at the same time, if something does go wrong, we need to let the programmer know somehow...
In this particular case though (G_IO_ERROR_CLOSED), the warning isn't at all useful, and due to the multi-threadedness of gdbus, I don't even think you can completely reliably prevent it by checking g_dbus_connection_is_closed() before g_method_invocation_return_value(). (Though NM could do that anyway to *mostly* get rid of it) So probably glib should skip the warning in this case.
(The warning could be hit from any D-Bus method return that might be on a private connection... which I think means every D-Bus method return in the daemon.)