Description of problem: When booting a fresh installed f9 beta, the I expect that firstboot runs. But when booting to init mode 5, the graphical boot is not completed, and no firstboot is shown. Only if booting in initmode 3, firstboot appears. Version-Release number of selected component (if applicable): How reproducible: Each time Steps to Reproduce: 1.Install F9 beta 2.boot for the first time 3. Actual results: No firstboot is shown Expected results: firstboot is shown Additional info:
Are there any /tmp/firstboot-* files? If so, please attach them to this bug report.
I'm sorry, no.
What do you mean by "the graphical boot is not completed"? Is something failing before firstboot has a chance to run, or is it only firstboot that is failing?
I have the same problem with F9-Preview. After text mode installation runlevel 5 is default in the inittab. During the first boot - the first boot is run in text mode but X server tries to start and everything hangs... I found the following workaround: If installed in text mode, run the first time in the text mode (runlevel 3), configure X and then run in runlevel 5. the solution I propose is such: If installed in text mode - the first boot is in runlevel 3 - without X server. The default runlevel can be detected and changed later in X configuration.
It would be great to have it fixed before final release as newbies may have trouble with it.
> What do you mean by "the graphical boot is not completed"? > Is something failing > before firstboot has a chance to run, or is it only firstboot that is failing? Nothing fails. My problem is exactly described in comment #4 by pliszka.edu
Okay, thanks for the detailed directions. I am now able to reproduce and see what's going on.
This should be fixed in tomorrow's rawhide I believe
Yep, just verified that it worked. Thanks for doing the rebuild.
I completed fresh 2 installations yesterday and today, and in both cases firstboot failed to run after rebooting into the new installations. I noticed that if I restart the system after firstboot failed, it will run only if switch rhgb to 'detail view' on restarting. And I also noticed it spewed out 2 lines of error saying something like 'loading language module failed, skipping' (sorry i could read the exact error, it went away too fast).
What tree did you install with?
(In reply to comment #11) > What tree did you install with? Rawhide
I noticed this on a rawhide install yesterday as well.
Can you attach /root/install.log and /var/log/anaconda.log from your install? I did a few installs with yesterday's rawhide and had firstboot come up fine.
Created attachment 304401 [details] anaconda log
Created attachment 304402 [details] rawhide install log
My testing shows that it works if rhgb is not running.
Traceback (most recent call last): File "/usr/sbin/firstboot", line 170, in <module> moduleList = loadModules(config.moduleDir, mode) File "/usr/lib64/python2.5/site-packages/firstboot/loader.py", line 93, in loadModules displayException(module=module) File "/usr/lib64/python2.5/site-packages/firstboot/exceptionWindow.py", line 95, in displayException ExceptionWindow(text, module=module) File "/usr/lib64/python2.5/site-packages/firstboot/exceptionWindow.py", line 32, in __init__ import gtk File "/usr/lib64/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 79, in <module> _init() File "/usr/lib64/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 67, in _init _gtk.init_check() RuntimeError: could not open display
Clearing 444010 - that's not the cause of this issue (at least not this incarnation of it.)
Fixed in rhgb-9.0.0-6.fc9.
Verified.