Bug 2000300 - gsd-usb-protect dumps core on first boot
Summary: gsd-usb-protect dumps core on first boot
Keywords:
Status: CLOSED DUPLICATE of bug 1950669
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rui Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F35FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2021-09-01 19:49 UTC by Brandon Nielsen
Modified: 2021-09-07 17:23 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-09-07 17:23:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Journal from initial boot after install (321.38 KB, text/plain)
2021-09-01 19:49 UTC, Brandon Nielsen
no flags Details

Description Brandon Nielsen 2021-09-01 19:49:31 UTC
Created attachment 1819745 [details]
Journal from initial boot after install

Description of problem: gsd-usb-protect dumps core on first boot, leading to a sad face before gnome-initial-setup appears (also appears to prolong the time it takes for gnome-initial-setup to appear).


Version-Release number of selected component (if applicable): 40.0.1-2.fc35.x86_64 from Fedora 35 20210831.n.1 compose[0].


How reproducible: Only tested a single install, cannot say.


Steps to Reproduce:
1. Install F35 Workstation Live
2. Reboot after install completes
3. Wait for gnome-initial-setup to appear, notice sad face appearing

Actual results: Sad face appears before gnome-initial-setup. "Process 1123 (gsd-usb-protect) of user 983 dumped core." appears in the journal.


Expected results: No sad face, gnome-initial-setup launching quickly.


Additional info: Journal from initial boot is attached.

[0] - https://kojipkgs.fedoraproject.org/compose/branched/Fedora-35-20210831.n.1/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-35-20210831.n.1.iso

Comment 1 Brandon Nielsen 2021-09-01 23:58:09 UTC
I can confirm this has happened on at least 2 installs in a row. System is x86_64, BIOS.

Comment 2 Fedora Blocker Bugs Application 2021-09-06 01:00:08 UTC
Proposed as a Blocker for 35-beta by Fedora user nielsenb using the blocker tracking app because:

 Violates the "SELinux and crash notifications" final release criterion due to generation of a crash report and a sad face on boot.

Comment 3 Brandon Nielsen 2021-09-06 01:10:48 UTC
I meant to propose this as a 35-final blocker as it violates the "SELinux and crash notifications"[0][1].

Also, I have not had time to dig into this. I have only tested on a single system.

[0] - https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#SELinux_and_crash_notifications
[1] - https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/TJBDNLJ2WK5SMDAYY7245YNRB2JIWJPZ/

Comment 4 Adam Williamson 2021-09-06 16:39:56 UTC
So, the delay on boot is not actually caused by this crash, we don't think. That is tracked at https://bugzilla.redhat.com/show_bug.cgi?id=1997310 . I don't know if it's clear what causes the sadface, but it *could* be this.

This crash has been around for some time, there is an F35 report at https://bugzilla.redhat.com/show_bug.cgi?id=1950669 and an F34 report at https://bugzilla.redhat.com/show_bug.cgi?id=1937073 ...

Comment 5 Adam Williamson 2021-09-07 17:23:19 UTC
Discussed at 2021-09-06 blocker/FE review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021/fedora-blocker-review.2021-09-06-16.00.html . We agreed to punt on this as the bug is based on what seems to be a false premise - that the gsd-usb-protection crash causes the delay to g-i-s startup.

We don't know for sure whether the gsd-usb-protect crash causes the sadface. We agreed to delay any decisions on blocker status till the SELinux issues are cleared up so we can see how things look without those.

I'm gonna close this as a dupe of the gsb-usb-protect crash, since we already have bug reports for both the actual issues here (gsd-usb-protect crash and g-i-s slowness).

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


Note You need to log in before you can comment on or make changes to this bug.