Description of problem: If a sysadmin decides to set firstboot to run at boot-time, and finds /etc/sysconfig/firstboot with "RUN_FIRSTBOOT=no" as its contents, it's not unreasonable to expect that setting "RUN_FIRSTBOOT=yes" will do the job. Version-Release number of selected component (if applicable): 1.4.3-1 How reproducible: Always Steps to Reproduce: 1. echo RUN_FIRSTBOOT=yes > /etc/sysconfig/firstboot 2. unset DISPLAY 3. /usr/sbin/firstboot --reconfig Actual results: Nothing. Expected results: Firstboot's TUI, in all its glory. Additional info: It looks like there's no "return True" statement to be called if "FIRSTBOOT=no" isn't found and we fall out of the "for" loop.