Description of problem: When booting a freshly-installed F35 Workstation system into the gnome-initial-setup session using a nightly image, the entire desktop session usually crashes to the "oh no, something has gone wrong!" screen. I tracked it down to a gsd-usb-protection-manager crash (apparently the entire session goes down when gsd-usb-protection-manager crashes) caused by what I believe to be a GLib bug, https://gitlab.gnome.org/GNOME/glib/-/issues/2486. Version-Release number of selected component (if applicable): glib2-2.69.2-1.fc35 How reproducible: Almost always, but not always. Seems to sometimes randomly not happen? But it usually happens. Steps to Reproduce: 1. Boot newly-installed system for first time Actual results: Fail whale ("Oh no, something has gone wrong!") displays Expected results: No fail whale Additional info: I will note that if you're testing in a virtual machine, the gnome-initial-setup window may fully cover the "oh no, something has gone wrong" crash dialog. This won't happen at larger screen sizes.
Proposed as a Blocker for 35-final by Fedora user catanzaro using the blocker tracking app because: There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop.
Created attachment 1822218 [details] screenshot of initial setup experience
Matthias found the crash occurs in F34 too: https://retrace.fedoraproject.org/faf/problems/bthash/?bth=2028d669804553141f239c56c6721219d8aa61ab&bth=07c8c1dc1596cd53b2e400ddc8e0f463a1833483&bth=321120928ed22118de06524cce254110b16efc46&bth=3d41088a958952e9d4885747aab4a54a8a54fa2a&bth=db4ee2df912d53ec22cb64b9d4c6a2fb40ea945d&bth=557fb9aae2e65ceb543e3ffc34353fc21067e137 Nice 10,158,564 reports there. I wonder what the record is....
Hm I missed something interesting: abrt hasn't seen this since March! O_O
(In reply to Michael Catanzaro from comment #4) > Hm I missed something interesting: abrt hasn't seen this since March! O_O Sorry, that is just a different crash altogether. Please ignore comment #3 and comment #4.
got one of these crashes in Rawhide earlier today
#agreed 2003285 - AcceptedBlocker, violates the following criterion: "If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test." While GIS does start, the error that is presented occludes this fact so isn’t a meaningful distinction.
Likely a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1950669 . We already had https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/585 upstream too.
Yes. *** This bug has been marked as a duplicate of bug 1950669 ***