Bug 929435 - initial-setup not starting on boot
Summary: initial-setup not starting on boot
Keywords:
Status: CLOSED DUPLICATE of bug 929403
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Sivák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F19Alpha, F19AlphaBlocker
TreeView+ depends on / blocked
 
Reported: 2013-03-30 15:23 UTC by satellitgo
Modified: 2013-04-02 09:12 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-02 09:09:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description satellitgo 2013-03-30 15:23:04 UTC
Description of problem:
OEM test basic-x plus LDXE:  anaconda does not allow root password to be left blank.After root password is entered; computer is rebooted and logged in as root; called "initial-setup" from terminal and added user and changed TZ  then logged out/in to newly created user.....

initial-setup is NOT called automatically on reboot....

Version-Release number of selected component (if applicable):

anaconda 19.14 with netinstall TC3 x86_64
basic-x plus LDXE selected

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
Not have to enter root password or user information on install for true oem install
initial-setup to be called on boot

Additional info:

Comment 1 Jens Petersen 2013-04-02 09:05:50 UTC
Well initial-setup is in comps, and installed.

So I think this is a initial-setup bug if it is not starting up.

(In reply to comment #0)
> OEM test basic-x plus LDXE:  anaconda does not allow root password to be
> left blank.

(Not sure what you mean by OEM here.)

Anyway I believe this is a feature currently: anaconda currently
enforces you either setup a root password or an admin user I think.

Comment 2 Jens Petersen 2013-04-02 09:09:25 UTC
Anyway I guess this is a duplicate of bug 929403.

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

Comment 3 Jens Petersen 2013-04-02 09:12:12 UTC
(Unless you want to go the other way and pursue the root password enforcement.)


Note You need to log in before you can comment on or make changes to this bug.