Bug 929439

Summary: When a local user was already created in anaconda, gnome-initial-setup still forces one to create a second local user
Product: [Fedora] Fedora Reporter: Mike FABIAN <mfabian>
Component: gnome-initial-setupAssignee: Jasper St. Pierre <jstpierr>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jstpierr, mclasen, robatino
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-04-02 10:22:56 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
gnome-initial-setup-forces-creation-of-local-user-although-there-is-alocal-user-already.png none

Description Mike FABIAN 2013-03-30 16:48:07 UTC
Created attachment 718305 [details]
gnome-initial-setup-forces-creation-of-local-user-although-there-is-alocal-user-already.png

- Install Fedora-19-Alpha-TC3-x86_64-DVD.iso
- use a default install for the Gnome desktop
- during the installation of the packages, create a local user in anaconda

After the reboot, gnome-initial-setup starts.

One of the steps in gnome-initial-setup is creating a local user.

gnome-initial-setup does not notice that this has been done already 
and does not allow to skip that step.

When trying to create a user with the same user name as the one
created during the installation, a warning triangle appears 
next to the username. So gnome-initial-setup somehow does seem
to have that information that a local user is already there, only
it does not use it to allow  to skip that step (see screenshot).

The “continue” button only becomes clickable when a second local user
is created.

Comment 1 Andre Robatino 2013-04-01 02:55:11 UTC
Looks like a duplicate of bug 929289.

Comment 2 Jens Petersen 2013-04-02 10:22:56 UTC

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