Bug 70757 - Help --> About does not work
Summary: Help --> About does not work
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-kickstart
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-08-04 23:17 UTC by Peter van Egdom
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-06 21:57:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Peter van Egdom 2002-08-04 23:17:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721

Description of problem:
In "redhat-config-kickstart" the Help --> About Window does not appear.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Start redhat-config-kickstart
2. Help --> About
3.
	

Actual Results:  About window does not appear.

When started from a xterm, the following text appears instead :

Traceback (most recent call last):
  File "/usr/share/redhat-config-kickstart/kickstartGui.py", 
   line 144, in on_about_activate
    dlg.set_position (gtk.CENTER)
  AttributeError: 'module' object has no attribute 'CENTER'


Expected Results:  An 'about' screen

Additional info:

Tried the latest version from RAWHIDE :
redhat-config-kickstart-2.3.2-5

Comment 1 Brent Fox 2002-08-06 04:07:58 UTC
Should be fixed in redhat-config-kickstart-2.3.2-6.  

QA, please verify.

Comment 2 Jay Turner 2002-08-06 11:52:31 UTC
I'm still getting this error with redhat-config-kickstart-2.3.2-6.

Comment 3 Brent Fox 2002-08-06 21:57:05 UTC
Sorry about that, there was a bug in the Makefile that caused an older version
of the kickstartGui.py to be used.  Try 2.3.2-7.

Comment 4 Jay Turner 2002-08-08 05:26:25 UTC
Fix confirmed with redhat-config-kickstart-2.3.2-8.


Note You need to log in before you can comment on or make changes to this bug.