Bug 1943683

Summary: "gnome-settings-daemon quit unexpectedly" after first login
Product: [Fedora] Fedora Reporter: Brandon Nielsen <nielsenb>
Component: gnome-settings-daemonAssignee: Rui Matos <tiagomatos>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: bugzilla, fmuellner, gnome-sig, mkasik, ofourdan, rstrode, tiagomatos, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-15 03:15:22 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:
Attachments:
Description Flags
Journal from initial boot none

Description Brandon Nielsen 2021-03-26 19:46:31 UTC 
Description of problem: After going through Gnome initial setup and logging in for the first time, abrt notifies of "gnome-settings-daemon quit unexpectedly".


Version-Release number of selected component (if applicable): 40.0.1.fc34


How reproducible: Every time, though I have only installed once.


Steps to Reproduce:
1. Install
2. Complete Gnome initial setup
3. Login

Actual results: abrt notifies of "gnome-settings-daemon quit unexpectedly".


Expected results: No error notification immediately after log in.


Additional info: ABRT report[0]. Will upload journal shortly.

[0] - https://retrace.fedoraproject.org/faf/reports/81992/
Comment 1 Brandon Nielsen 2021-03-26 20:01:59 UTC 
Created attachment 1766753 [details]
Journal from initial boot
Comment 2 Brandon Nielsen 2021-04-09 16:29:31 UTC 
Still seen with 20210407 compose[0].

[0] - https://kojipkgs.fedoraproject.org/compose/branched/Fedora-34-20210407.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-34-20210407.n.0.iso
Comment 3 Brandon Nielsen 2021-04-14 19:55:56 UTC 
Bug #1946129 is the likely cause of this bug.
Comment 4 Chris Murphy 2021-04-15 03:15:22 UTC 
Could folks make sure you're fully up to date and see if the problem is still occurring? And if you can, please attach 'journalctl --user -b' to bug 1937073, thanks.

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