It just got pushed to stable, so too late to hold this off.
I believe gtk upstream intends to have gtk point releases suitable for everywhere though, that's why there are no branches for different gnome versions. I'd suggest to bring this up with upstream first.
@dan1mal, We have a concept of updates that are being tested before being pushed to the base repository. This update is currently in "testing" state, and once it is verified to not cause additional issues compared to what's in the base repo, then it's moved to "stable". These two states correspond to the /etc/yum.repos.d/fedora.repo ("stable") and /etc/yum.repos.d/fedora-updates-testing.repo ("testing") repos.
The main thing here that's important to verify during testing is that it doesn't cause additional issues compared to what's in stable (doesn't cause regressions). No regressions mean that this update should be good to move to stable.
This doesn't mean that it's not important to find non-regression issues, but these should go to a bug tracking system and not block this update from being moved to stable. That's why I asked if this is a regression or not :)
Re https://gitlab.gnome.org/GNOME/gnome-control-center/issues/401, I doubt that's the same issue you are running into. Probably worth filing a new one and adding screenshots and anything that looks like relevant from 'journalctl -a -b'.
Also, could someone file a bug against https://gitlab.gnome.org/GNOME/gnome-control-center and report the online accounts issue? It could also be a gnome-online-accounts bug, not gnome-control-center, but it doesn't super much matter which one to file against. Thanks!
You can downgrade gitg to a non-segfaulting version by doing 'dnf distro-sync gitg'. The problematic gitg 3.32.0 update was unpushed and is no longer in updates-testing. See https://bodhi.fedoraproject.org/updates/FEDORA-2019-7ee71eae68