Bug 108254

Summary: redhat-config-boot fails to run
Product: [Fedora] Fedora Reporter: Andre Robatino <robatino>
Component: redhat-config-bootAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:59:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Andre Robatino 2003-10-28 18:40:27 UTC
Description of problem:
  redhat-config-boot fails to start from the menu.  When run from the command
line, it generates the following error messages:

[root@localhost andre]# redhat-config-boot
Traceback (most recent call last):
  File "/usr/share/redhat-config-boot/redhat-config-boot.py", line 22, in ?
    app.stand_alone()
  File "/usr/share/firstboot/modules/boot_gui.py", line 275, in stand_alone
    self.setupScreen()
  File "/usr/share/firstboot/modules/boot_gui.py", line 87, in setupScreen
    self.setDefault()
  File "/usr/share/firstboot/modules/boot_gui.py", line 178, in setDefault
    self.timeoutEntry.set_value(self.probedTimeout)
AttributeError: BootWindow instance has no attribute 'probedTimeout'
[root@localhost andre]#

Version-Release number of selected component (if applicable):
redhat-config-boot-0.1.5-1

How reproducible:
always

Steps to Reproduce:
1.  Try to run redhat-config-boot from the command line.
    
Actual results:
  Crashes and burns with above error messages.

Expected results:
  Should bring up GUI.

Additional info:
  The previous version of redhat-config-boot worked properly.

Comment 1 Bill Nottingham 2003-10-28 22:02:43 UTC

*** This bug has been marked as a duplicate of 106796 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:59:31 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.