Description of problem: Firstboot, when run automatically after kickstart, fails as soon as it's started, with the following message: Traceback (most recent call last): File "/usr/share/firstboot/firstbootWindow.py", line 502, in loadModules vbox, pix, title = module.launch() File "/usr/src/build/430919-i386/install/usr/share/firstboot/modules/boot_gui.py", line 177, in launch return FirstbootGuiWindow.launch(self) File "/usr/lib/python2.3/site-packages/rhpl/firstboot_gui_window.py", line 106, in launch internalVBox.pack_start(self.myVbox, gtk.TRUE) AttributeError: BootWindow instance has no attribute 'myVbox' After clicking OK, firstboot continues. How reproducible: If firstboot is killed and restarted, then the error is repeated, but I'm not sure it happens on every install. Steps to Reproduce: 1. boot from boot.iso, start kickstart 2. run install, reboot, wait for firstboot Additional info: Adding --debug to firstboot works around it. (Of course, then firstboot doesn't do much). (See boot_gui.py:176) I suppose the kickstart options are relevant. The ks.cfg is available if required.
# rpm -qf /usr/lib/python2.3/site-packages/rhpl/firstboot_gui_window.py rhpl-??? please report the rhpl version number
Created attachment 120426 [details] Stratus kickstart file (for customers) test case
output from rpm version command on Stratus system running RHEL4-U2-GA is the following: rhpl-0.148.3-1
Marking as a duplicate of a later bug because that one's already been added to the proposed list. *** This bug has been marked as a duplicate of 178920 ***
A Stratus customer is hitting this bug at install time. From Charlotte Richardson (Stratus): The symptom is that the RedHat firstboot window boot_gui.py blows up (and doesn't configure the grub.conf file as a result) because self.myVbox does not exist when the launch function in the python script calls FirstbootGuiWindow unless doDebug is set. This seems to occur because self.setupScreen, which creates the myVbox attribute along with many others, only runs in the launch function if doDebug is set. You can see in the stand_alone function it runs in either case before FirstbootGuiWindow runs. It appears that this is the problem: the launch function should run setupScreen whether or not doDebug is set.