Bug 2003285

Summary: gsd-usb-protection-manager crash in get_current_screen_saver_status
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanza>
Component: glib2Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 35CC: awilliam, caillon+fedoraproject, droidbittin, gnome-sig, lruzicka, mclasen, rhughes, robatino, rstrode, sandmann, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: AcceptedFinalBlocker
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-15 17:06:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1891955    
Attachments:
Description Flags
screenshot of initial setup experience none

Description Michael Catanzaro 2021-09-10 21:34:11 UTC 
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.
Comment 1 Fedora Blocker Bugs Application 2021-09-10 21:34:52 UTC 
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.
Comment 2 Michael Catanzaro 2021-09-10 21:35:12 UTC 
Created attachment 1822218 [details]
screenshot of initial setup experience
Comment 3 Michael Catanzaro 2021-09-10 21:47:31 UTC Comment hidden (obsolete)
Comment 4 Michael Catanzaro 2021-09-10 21:48:15 UTC Comment hidden (obsolete)
Comment 5 Michael Catanzaro 2021-09-10 21:49:52 UTC Comment hidden (obsolete)
Comment 6 Luna Jernberg 2021-09-13 16:57:00 UTC 
got one of these crashes in Rawhide earlier today
Comment 7 Lukas Ruzicka (Red Hat) 2021-09-13 17:19:02 UTC 
#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.
Comment 8 Adam Williamson (Red Hat non-Fedora) 2021-09-15 15:18:08 UTC 
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.
Comment 9 Michael Catanzaro 2021-09-15 17:06:49 UTC 
Yes.

*** This bug has been marked as a duplicate of bug 1950669 ***