Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1505997

Summary:	gnome-initial-setup does not run on first boot on Workstation images
Product:	[Fedora] Fedora	Reporter:	Paul Whalen <pwhalen>
Component:	gnome-initial-setup	Assignee:	Rui Matos <tiagomatos>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	awilliam, gnome-sig, jstpierr, pwhalen, tiagomatos
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-25 13:18:37 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:	245418, 1396705

Description Paul Whalen 2017-10-24 18:48:25 UTC

Description of problem:
gnome-initial-setup does not run on first boot on armhfp and aarch64 Workstation images, instead boots to log in screen. 

Version-Release number of selected component (if applicable):
gnome-initial-setup-3.26.0-1.fc27

How reproducible:
Everytime

Steps to Reproduce:
1. Boot a recent workstation image on arm or aarch64


Actual results:
Boot to log in screen

Expected results:
gnome-initial-setup

Additional info:
Related bug? - https://bugzilla.redhat.com/show_bug.cgi?id=1502827

Comment 1 Paul Whalen 2017-10-24 18:56:25 UTC

Nominating as a FE for final. Workstation is not considered release blocking on arm (or aarch64) but would be rather unfortunate to have not working for the final release.

Comment 2 Adam Williamson 2017-10-24 22:38:21 UTC

sounds very likely to be a duplicate of #1502827 . can you test if gdm-3.26.1-2.fc27 fixes it?

Comment 3 Paul Whalen 2017-10-25 13:18:37 UTC

gdm-3.26.1-2.fc27 does indeed fix it. Closing as a duplicate.

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