Description of problem: After installing FC5 Test 3 and successfully performing firstboot config. First boot is not disabled and runs at every boot though the config part of it is never seen. Version-Release number of selected component (if applicable): 1.4.4-1 How reproducible: Steps to Reproduce: 1. Install FC5 Test 3 in vmware or x86 boxen. 2. Reboot and perform firstboot config. 3. Reboot as many times as you like and watch firstboot being executed during boot and visible through rhgb. Additional info: A check into system-config-services shows firstboot is still checked to run and not disabled.
The service itself isn't actually running. What's happening here is that the init script for it is checking for a lock file to determine whether it should run or not. This is to prevent the pretty weird corner case of if firstboot fails to start in runlevel 5 for some reason (for instance, X is all screwed up) but then you switch into runlevel 3 to fix it. Without some extra protection, firstboot will attempt to start again on the terminal. See bug 145169.
*** Bug 197551 has been marked as a duplicate of this bug. ***