Bug 516730

Summary:	[Rawhide][Firstboot] - Firstboot Not Creating Username
Product:	[Fedora] Fedora	Reporter:	Satyabrata Maitra <smaitra>
Component:	firstboot	Assignee:	Chris Lumens <clumens>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	clumens
Target Milestone:	---	Keywords:	Desktop
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-08-11 14:34:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Satyabrata Maitra 2009-08-11 10:25:10 UTC

Description of problem:
When install rawhide (Fedora Release 11.90) for i386 arch, after the installation, firstboot is not running and due to this its opening an unusual login window without any username list. Users can be confused with no username and password text box window.

Version-Release number of selected component (if applicable):
firstboot-1.107-1.fc12.i686
kernel-2.6.31-0.125.rc5.git2.fc12.i686.PAE

How reproducible:
Always, but tried it once only!

Steps to Reproduce:
1. Install the rawhide for FC12. Can follow the repo also :
   http://nighthawk.englab.pnq.redhat.com/redhat/fedora/linux/development/rawhide-20090809/i386/os/
2. Let the system installed
3. Reboot the system
4. Wait and see what appears in login window.
  
Actual results:
Firstboot is not running properly

Expected results:
Firstboot should run properly after the installation and reboot and it should let the user to create an account.

Additional info:

Comment 1 Satyabrata Maitra 2009-08-11 10:55:10 UTC

Adding the user with useradd command from any other console, can instantly resolve the problem, but still, its better if user can be created through firstboot UI.

Comment 2 Chris Lumens 2009-08-11 14:34:37 UTC


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