With glib 2.77.0, libnm-glib-aux's `_ctx_integ_source_reacquire` hits a new critical warning in glib and causes console spam (in anaconda, Steam client...)
See https://gitlab.gnome.org/GNOME/glib/-/issues/3054 and https://bugzilla.redhat.com/show_bug.cgi?id=2224009 for a lot of the background here.
A new check was added to glib in 2.77.0 which, AFAICT, complains about more or less exactly what NM is intentionally trying to do in _ctx_integ_source_reacquire
. In this later commit, a return statement was added to the check to prevent anaconda flat out crashing on it (which was the bug reported in https://gitlab.gnome.org/GNOME/glib/-/issues/3054 ). With the current state, nothing we know of crashes, but both anaconda and Steam client (and maybe some other things) flood the console with warnings:
nm-CRITICAL **: 19:27:07.444: file src/libnm-glib-aux/nm-shared-utils.c: line 4959 (<dropped>): should not be reached
I think I understand, more or less, what's going on, but not in enough detail to have any idea about how to fix it. I'm not sure if NM needs to be adjusted somehow, or we need to fix the NM-based apps to not do the wrong stuff with context acquisition which NM is trying to clean up after them.
The console spam is a particular problem for anaconda because it causes messages that ought to be visible to the user (like instructions on connecting via VNC) to scroll off the screen. I'm not sure if it affects the text install mode, but if it does that would be a significant issue also.