Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 78150 - Buttons dead when relnotes are displayed
Summary: Buttons dead when relnotes are displayed
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-19 13:57 UTC by David Balažic
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version: FC1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-01-10 15:45:10 UTC

Attachments (Terms of Use)

Description David Balažic 2002-11-19 13:57:30 UTC
Description of Problem:

GUI install : When the release notes are displayed, the buttons "Hide 
Help", "Back" and "Next" are not ghosted, but can't be clicked either.

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

red hat linux 8.0

How Reproducible:


Steps to Reproduce:
1. click "Release Notes" during GUI install 

Actual Results:

A window with relnotes appears. The buttons on the backgrond windows
don't respond while the relnotes are displayed.

Expected Results:

The buttons on the background should be ghosted ( grayed ) out or they should 
work as normaly.

Additional Information:

Comment 1 Jeremy Katz 2003-01-10 07:39:52 UTC
Fixed in CVS

Comment 2 Alan Horkan 2003-02-14 12:31:23 UTC
i think i encountered something fairly similar but I was able to work around it 
as the Alt+O mnuemonic (sp?) worked.  

Comment 3 David Balažic 2003-03-27 08:40:55 UTC
It is still the same in the latest release ( you know which one ).

Comment 4 Michael Fulbright 2003-07-01 18:26:35 UTC

Comment 5 David Balažic 2004-01-10 15:45:10 UTC
In FC1, the button are corretly ghosted when inactive.
Marking as resolved.

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