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.

Cloned to a separate BZ from bug 1873561 per comment https://bugzilla.redhat.com/show_bug.cgi?id=1873561#c22

there really isn't much to do here.

The functions are now documented to use with care (ie: don't use them via bindings!):
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b012877445bddd772eec79e3ce38f93cc40de720


An alternative fix would be to add new, alternative API that doesn't have this problem. However, these 2 functions are rather trivial. I think we don't need to add them, just implement them yourself. You can do so using nm_access_point_connection_valid() and nm_device_connection_valid() -- these latter two are not trivial, but luckily they are part of public API already.


Yet another alternative fix would be to adjust the annotation so that binds work. However, since gobject-bindings doesn't seem to have a clear way how to do that [1], and because different bindings (vala, pygobject) disagree how this is handled, there is no real fix. So, unless [1] is fixed this is not doable. And even then, we would have to take care that it does not break what currently is working: e.g. using these functions from vala currently works and it should keep working. Using them from pygobject was broken for the last two years due to [2].


[1] https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/305
[2] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/201c153e25990f61421be9984ecca5bc71be5845



I'll close this as WONTFIX. Please reopen if you disagree or have a suggestion.