Red Hat Bugzilla – Bug 70211
Firstboot never appears after installation
Last modified: 2008-05-01 11:38:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724
Description of problem:
After installing limbo 7.3.93, firstboot flickers the screen a few times and
fails to appear. X starts up and GDM then appears.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3.Watch firstboot fail to come up
Actual Results: Screen flickers, and X starts up without firstboot
Expected Results: Firstboot should appear before X starts
I seem to remember firstboot working correctly with the first limo beta.
Can you attach your /var/log/messages file?
Created attachment 68345 [details]
Another try at the /var/log/messages file
Created attachment 68346 [details]
Here is the xfree log
Symtoms of this bug look like bug # 68743.
Jul 30 22:29:53 linux firstboot: Window manager error: Unable to open X display :1
Jul 30 22:29:53 linux firstboot:
Jul 30 22:29:53 linux firstboot: ** (--display=:1:816): WARNING **:
CORBA_ORB_destroy: ORB still has 2 refs.
Jul 30 22:29:53 linux firstboot: in start_existing_X
Jul 30 22:29:53 linux firstboot: Traceback (most recent call last):
Jul 30 22:29:53 linux firstboot: File "/usr/sbin/firstboot", line 120, in ?
Jul 30 22:29:53 linux firstboot: firstbootWindow.firstbootWindow(wm_pid,
Jul 30 22:29:53 linux firstboot: AttributeError: 'module' object has no
I did several fresh installs (all custom) of Limbo2 on several systems in the
past 2 days. On my laptop firstboot always fails to run with this exact problem
of trying to connect to display :1. It failed perhaps 5 other times on some of
my desktops, and I have seen it run properly only once.
Tested Rawhide firstboot-0.9.9-1 on all these systems too. Still same problem.
BTW, can firstboot please be removed from init 3?
I believe that this problem has been fixed with firstboot-0.9.9-7 or later. In
addition, I have set firstboot to only run in runlevel 5.
QA, please verify. This is the race condition bug that we have seen on a few
machines. I have been unable to reproduce it after the fix I added yesterday.
I'm no longer seeing this race on any of the machines that I'm testing with.
Closing as fixed in firstboot-0.9.9-13.