Created attachment 1015957 [details]
Screenshot of initial setup gui scren

Description of problem:

initial-setup is started even if kickstart file contains a line

firstboot --disable


According to Fedora 21 Installation Guide section A.7.1
https://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-kickstart-commands-after.html#sect-kickstart-commands-firstboot

initial setup should not start when the kickstart file contains the option as listed above.

Also note that the default of this option is disabled, as declared on the same page of the installation guide: "If not specified, this option is disabled by default."


I looked about the files of the package and found that in
/usr/lib/python2.7/site-packages/initial_setup/__main__.py
the file /root/anaconda-ks.cfg is parsed.
But I found nothing that checks for the existence of the "firstboot" option.



Version-Release number of selected component (if applicable):
initial-setup-0.3.25-1.fc21.x86_64
initial-setup-gui-0.3.25-1.fc21.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Install Fedora 21 non-product with a kickstart file
   that contains at least the lines

firstboot --disable
xconfig --defaultdesktop=GNOME --startxonboot

  and other options that would be asked by initial-setup, but does not create a non-root user

auth --useshadow --passalgo=sha512
rootpw ...
network ...

   and installs packages initial-setup and initial-setup-gui.


2. Check the graphical console after kickstart installation has finished.

Actual results:

initial-setup is running.

root       875     1  0 00:15 ?        00:00:00 /bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp
root      1138   875  0 00:15 ?        00:00:00 /bin/sh /bin/firstboot-windowmanager /bin/initial-setup
root      1155  1138  0 00:15 ?        00:00:00 /bin/sh /bin/initial-setup
root      1160  1155  0 00:15 ?        00:00:13 python -m initial_setup

# systemctl status initial-setup-graphical.service
● initial-setup-graphical.service - Initial Setup configuration program
   Loaded: loaded (/usr/lib/systemd/system/initial-setup-graphical.service; enabled)
   Active: activating (start) since So 2015-04-19 00:15:10 CEST; 1h 59min ago
  Process: 718 ExecStartPre=/bin/plymouth quit (code=exited, status=0/SUCCESS)
 Main PID: 875 (xinit)
   CGroup: /system.slice/initial-setup-graphical.service
           ├─ 875 /bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp
           ├─ 881 /usr/libexec/Xorg.bin :9 -ac -nolisten tcp
           ├─1138 /bin/sh /bin/firstboot-windowmanager /bin/initial-setup
           ├─1151 /usr/bin/xfwm4
           ├─1155 /bin/sh /bin/initial-setup
           ├─1160 python -m initial_setup
           ├─1222 /bin/dbus-launch --autolaunch c82bbcaee24c3e457894dcf3f5167366 --binary-syntax --close-stderr
           ├─1239 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
           ├─1243 /usr/lib64/xfce4/xfconf/xfconfd
           ├─1361 /usr/libexec/at-spi-bus-launcher
           ├─1365 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
           └─1369 /usr/libexec/at-spi2-registryd --use-gnome-session

Apr 19 00:15:15 myhost.example.com org.a11y.Bus[1239]: Activating service name='org.a11y.atspi.Registry'
Apr 19 00:15:15 myhost.example.com org.a11y.Bus[1239]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 19 00:15:15 myhost.example.com org.a11y.atspi.Registry[1365]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 19 00:15:15 myhost.example.com org.a11y.atspi.Registry[1365]: Xlib:  extension "XEVIE" missing on display ":9".
Apr 19 00:15:15 myhost.example.com initial-setup[1160]: initializing GUI
Apr 19 00:15:15 myhost.example.com initial-setup[1160]: setting up the UI
Apr 19 00:15:15 myhost.example.com initial-setup[1160]: starting the UI
Apr 19 00:15:15 myhost.example.com anaconda[1160]: Entered hub: InitialSetupMainHub


Expected results:

Initial setup was not started.