Bug 960964

Summary:	Why is it that whenever I get g-i-s update and I reboot machine, I need to go through its setup
Product:	[Fedora] Fedora	Reporter:	Parag Nemade <pnemade>
Component:	gnome-initial-setup	Assignee:	Jasper St. Pierre <jstpierr>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bitlord0xff, jstpierr, mclasen, tiagomatos
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-05-08 14:54:44 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:

Description Parag Nemade 2013-05-08 12:16:31 UTC

Description of problem:
I install first Alpha RC4 and got g-i-s setup which I did. Then I updated sometime back same happened and now today I update to F19 Beta RC3 tree and got g-i-s setup window popup. Why am I being asked to go through this setup again and again.

Version-Release number of selected component (if applicable):
gnome-initial-setup-0.9-1.fc19.x86_64

How reproducible:
maybe always

Steps to Reproduce:
1.
2.
3.
  
Actual results:
once g-i-s setup completed , every update to it needs re-setup

Expected results:
should not ask setup again.

Additional info:

Comment 1 Matthias Clasen 2013-05-08 14:54:44 UTC

You are not being asked again and again. 
We've added the feature to run gnome-initial-setup the first time you log into an account that was not created by g-i-s. So, you got g-i-s again because the first time you ran it, the run-in-session feature did not exist yet, so it didn't mark your user account as 'done'. 

It should not happen again. If it does, please repoen the bug.

Comment 2 Parag Nemade 2013-05-08 15:02:11 UTC

Thanks for the explanation

Comment 3 Rui Matos 2013-05-17 16:18:25 UTC

*** Bug 953766 has been marked as a duplicate of this bug. ***