This is the Gnome 50~beta rebase.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2026-ec6ab2695b
Please log in to add feedback.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
Several missing rebuilds:
gnome-kiosk causes the openQA test failures as it's a dependency of anaconda, but they should all be fixed. This keeps happening; does mclazy need an update to know about these?
xhorak edited this update.
New build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
xhorak edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
Looks like msgraph was bumped on its own while this was in flight so the msgraph in this update is older than the current stable one. Need to bump and rebuild msgraph on the side tag so it's newer than that one.
xhorak edited this update.
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
So I'm seeing two remaining issues. One, both printing tests fail because the print dialog doesn't open. That looks like it's caused by xdg-desktop-portal crashing (there's repeated crashes logged in the journal). I'll backtrace that soon.
Two, after installing the update and rebooting on aarch64, we fail to reach GDM, and we also can't switch to a VT. If I make the system boot to runlevel 3, though, it does get to a VT fine. The journal from the failed boot seems not to give any indication of the problem, though :(
Figured out the xdg-desktop-portal-gnome crash (thanks Elliott), we need https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/merge_requests/249 , either backported somehow (tricky as it's a subproject) or just a new upstream release of x-d-p-gnome to package.
aarch64 thing is still a mystery.
so, for the aarch64 thing, I managed to hack stuff up so I can ssh into the test VM while it's in the state where GDM isn't appearing. but I'm not sure what to do now I'm in.
There's a gdm process, there's no gnome-shell process. this is all there is for gdm.service logs:
This is a backtrace of the running gdm process:
what else can I do to figure this out?
Aha. With gdm debug logging I'm seeing this:
so I'm suspecting this is gonna be https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/343 . I'm just re-confirming ATM (I've only seen this after a 'systemctl restart gdm.service' so far, confirming now that it happens even on the normal automatic start of gdm).
yeah, confirmed. I've filed an upstream issue for now. Can poke more on this tomorrow.
Could you update
gnome-shellstraight to the50.beta, please? It had been released only few hours ago, thus it was not ready before you created this update. It contains important changes for gnome-software, which would be good to have ready for the next week (and even if not, the50.betais supposed to be released this week in general, thus getting the latest bits is better) .Fix for the aarch64 gdm issue building on this side tag as https://koji.fedoraproject.org/koji/taskinfo?taskID=141935681 . It'll be pulled in whenever @xhorak is ready to re-generate the update with other new builds.
xhorak edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
adamwill edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been unpushed.
This update was unpushed as part of Fedora 44 Mass Branching because it failed gating tests. Please resubmit these changes for F44 and/or F45/Rawhide.
Sigh, so, latest problem: gnome-shell is crashing on aarch64 due to an undefined symbol:
no idea as of yet why it's undefined on aarch64 only (apparently). Can't debug ATM because Koji is down for branching.
OK, we (mainly @catanzaro) figured that out. Koji is down for branching ATM. Once it's back up we need to backport that, and also do an xdg-desktop-portal-gnome build with the crash fix in it - either backport the subproject update somehow (additional source tarball, I guess) or get a 50.beta release of x-d-p-g.
OK, we figured that out too. The fix is pushed and ready to build once branching is done, at least if we can figure out any signing issues or whatever.
We'll have to rebuild everything for Rawhide too as a separate update, of course.
adamwill edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'ignored'.
This update has been submitted for stable by bodhi
This got pushed because critpath generation for F44 is broken so it wasn't considered critpath any more so it wasn't gated :| we'll have to hope it works OK. openQA tests on 44 are a bit busted right now, I will try to fix things up in the morning and re-run tests to find out where we stand.