Bug 922951

Summary: gnome-initial-setup is enabled by default (and presently crashes)
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: gnome-initial-setupAssignee: Jasper St. Pierre <jstpierr>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: awilliam, jreznik, jstpierr, mclasen, petersen, robatino, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-21 12:19:02 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: 834084    
Attachments:
Description Flags
failure screenshot
none
journalctl output none

Description Kamil Páral 2013-03-18 20:55:55 UTC 
Description of problem:
If you install F19 and boot, you'll see a 'sad face' error. I've found out it comes from gnome-initial-setup. I have tried it just in VMs, but for many times and it seems to happen always. I don't know how to debug this and provide more info, instructions welcome.

Version-Release number of selected component (if applicable):
gnome-initial-setup-0.7-1.fc19.x86_64
gdm-3.7.91-1.fc19.x86_64
gnome-shell-3.7.91-1.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot F19 in a VM
Comment 1 Kamil Páral 2013-03-18 20:56:27 UTC 
Created attachment 712242 [details]
failure screenshot
Comment 2 Kamil Páral 2013-03-18 20:56:53 UTC 
Created attachment 712243 [details]
journalctl output
Comment 3 Colin Walters 2013-03-20 01:17:56 UTC 
Hmm.  This bit looks wrong:

if [ $1 -eq 1 ] ; then
    # Initial installation
    /usr/bin/systemctl enable gnome-initial-setup.service &>/dev/null || :
fi

Do we really want g-i-s enabled by default when installed in Fedora at this time?  I don't know what the intersection plan is between anaconda/firstboot/g-i-s or if there is even a plan, but regardless I suspect installing the package shouldn't enable it, it should be done explicitly by anaconda.
Comment 4 Kamil Páral 2013-03-20 09:18:21 UTC 
I think we should keep this bug related to the crash and discuss the startup conditions in bug 922885.
Comment 5 Adam Williamson 2013-03-20 09:27:52 UTC 
colin: comps has gnome-initial-setup as part of the GNOME group and firstboot in all the other desktop groups. christ alone knows what'll happen if you install two desktops, but it should work correctly in single-desktop cases (or 'any combination not including GNOME' cases).

kamil: 0.8 fixes the sadface but gives you https://bugzilla.redhat.com/show_bug.cgi?id=923501 in exchange.
Comment 6 Adam Williamson 2013-03-20 17:03:56 UTC 
Discussed at 2013-03-20 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-blocker-review-2.2013-03-20-16.00.log.txt . This is obviously a blocker, but we believe it's probably 'fixed' in 0.8 (0.8 breaks differently! see https://bugzilla.redhat.com/show_bug.cgi?id=923501 ), so Kamil is going to verify that 0.8 behaves the same for him as for me, then we will close this bug.
Comment 7 Adam Williamson 2013-03-21 06:46:58 UTC 
Still just waiting for Kamil's confirmation, but I've tested the current 0.8-3 build and it works fine for me.
Comment 8 Kamil Páral 2013-03-21 12:19:02 UTC 
With 0.8-3 this crash is gone, but I see bug 923501 instead.