Red Hat Bugzilla – Bug 68135
First time setup agent is never started
Last modified: 2007-04-18 12:43:55 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 Description of problem: In the LIMBO release notes you mention a first time setup agent which should be automatically started when the system boots for the first time after a fresh install. The agent didn't start on my system. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Do a fresh LIMBO install 2. Watch if first time setup agent get's started 3. Additional info:
Error found! This is a GUI only tool. I disabled graphical login during install and so couldn't see this agent. But it suddenly appeared after "init 5".
I have changed the default behavior to start firstboot in both runlevels 5 and 3. I plan to leave it like this for the next public beta. However, people may complain about having a GUI app start in runlevel 3. If a sizable number of people complain, then the options are to create a text mode for firstboot (problaby not time for this release) or to have firstboot set to never run if the user selects non-graphical login in the installer. This would prevent firstboot from starting up on random runlevel changes. As it is now, firstboot is going to run that first time, and once it runs, it will never run again, so the behavior you reported does not happen anymore. Thanks for your report.
How do you intend to run a GUI app in runlevel 3? I would REALLY prefer to see an additional text mode firstboot version.
It starts an X server to run firstboot in and then kills it when firstboot is finished.
What happens when I didn't configure X at installation time? Most of our server don't have X configured at all.
Please do NOT run firstboot even during the first init 3. Some people like nForce motherboards owners cannot allow X to run because it causes a complete hard lock.
Ok, I've changed firstboot to never start in runlevel 3. However, it will run the first time the machine enters runlevel 5. Should be fixed in firstboot-0.9.9-9 QA, please verify that this is the current behavior.
*** Bug 70259 has been marked as a duplicate of this bug. ***
Fix confirmed in firstboot-0.9.9-13.