GNOME 45.rc, together with libei 1.1.0 version update that's required by gnome-connections.
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-2023-d422824191Please login to add feedback.
This update has been submitted for testing by kalev.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted gtk4-4.12.1-1.fc39, and has inherited its bugs and notes.
This update has obsoleted nautilus-45~beta2-1.fc39, and has inherited its bugs and notes.
kalev edited this update.
Note that gnome-connections build that's included here depends on libei update from https://bodhi.fedoraproject.org/updates/FEDORA-2023-f065bb37ae . If this should cause openqa test issues, we'll have to merge the two updates.
This update's test gating status has been changed to 'failed'.
kalev edited this update.
New build(s):
Karma has been reset.
This update has obsoleted libei-1.1.0-1.fc39, and has inherited its bugs and notes.
kalev edited this update.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
rathann edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by rathann.
This update's test gating status has been changed to 'waiting'.
Works for me.
This update's test gating status has been changed to 'passed'.
rathann edited this update.
makes the session crash when trying to open a video on telegram
update_inhibitation (libmutter-13.so.0 + 0x164493)
@miniprise Thanks! Could you try to get a better backtrace with debug symbols, and file it as an issue upstream over at https://gitlab.gnome.org/GNOME/mutter/-/issues please?
hey @kalev are there any instructions to get it for fedora silverblue?
Hm, it can be a bit tricky as the whole session is crashing. I think the best strategy would be to use coredumpctl and try to get the backtrace for the already occurred crash that it captured. Just typing 'coredumpctl' lists all the crashes it has captured and 'coredumpctl gdb' should let you get the backtrace for the last crash. Hopefully it asks if you want to use debuginfod, which should make it all work nicely on Silverblue without having to overlay install tons of -debuginfo rpms.
Sorry, I don't have a Silverblue installation at hand to check the exact commands and if gdb is already installed in the base system or not, but hopefully it gets you started.
And thanks a lot for taking the time to look into it!
I hope this helps. https://gitlab.gnome.org/GNOME/mutter/-/issues/3014 (had to set DEBUGINFOD_URLS=https://debuginfod.fedoraproject.org/ to make gdb download debuginfo idk why its not set on silverblue)
Excellent, thanks!
the Silverblue installer gnome-kiosk crash is kinda mysterious, but...it's not happening in Rawhide, where most of this stuff has landed already. it's not a gating test, so gating is passed. I guess when this goes stable we'll see if the problem persists...
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@adamwill Hm, which one is it? update.install_default_update_ostree? I see one test there where it says it has soft failed - _graphical_wait_login (https://openqa.fedoraproject.org/tests/2127789#step/_graphical_wait_login/6), and then clicking on it it says:
Soft Failure:
geolocation failed!
I don't see anything about gnome-kiosk crashing?
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by kalev.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
This update has been pushed to stable.