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, 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 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!

@alciregi, @dan1mal: are the online accounts issues a regression compared to what's in F31 stable?

Let's unpush this one as well as the rest of the updates that depend on module(libgit2:0.28) already got unpushed.

Yes, sorry, I messed up a bit by putting babl and gegl04 into separate Bodhi updates. They are in stable now though, so once the mirrors sync up, it should all work out fine.

Great, thanks for testing it, @martinpitt!

Could you file an issue for this at please?

@dpward, Hm, good question. There's really no dependency between flatpak and flatpak-libs (the latter is for clients such as gnome-software and the flatpak CLI doesn't use it).

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

Let's submit both to testing then, with autokarma disabled, and then manually submit to stable at the same time.

(Edited the update to remove libgit2-glib- so we can submit it separately)

What's the plan with this? New xdg-desktop-portal 1.4.x releases depend on pipewire 0.2.6

Aha, looks like was unpushed. Let's keep this out of updates-testing as well for now then.

Note that this depends on pipewire-0.2.6-1.fc30 which is submitted separately. I've turned off autopush so that it doesn't go stable before the required pipewire update.

@atim Thanks. I've linked the bug now.

This update has been unpushed.