Bug 108764 - Password field locked during install
Summary: Password field locked during install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-01 09:44 UTC by Xander D Harkness
Modified: 2016-06-07 22:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-11-01 16:56:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Xander D Harkness 2003-11-01 09:44:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.6a)
Gecko/20031018

Description of problem:
Upon install a user missed while trying to click and drag across the
partition field size in disk druid.  His intention was to select the
partition size and type in a new value rather than use the increase /
decrease buttons.

The size was successfully chosen; however this seems to have an effect
three screens in when being asked to set the root password.  The
password entry fields are locked and the install cannot progress until
a root password is entered.  The only choice is to reboot.  Going
backwards and then forwards does not resolve this.

Version-Release number of selected component (if applicable):
anaconda-9.0-4  (First release on install ISO)

How reproducible:
Sometimes

Steps to Reproduce:
1.drag across the new partition size in disk druid without actually
managing to select the text (i.e. miss)
2.complete entries in disk druid
3.try to complete installation and enter root password - fields are
not available
    

Actual Results:  The fields are empty but will not accept text; cannot
complete the installation

Expected Results:  The root password should have been entered and the
installation continue.

Additional info:

Comment 1 Jeremy Katz 2003-11-01 16:56:11 UTC
This is fixed for FC1.  The workaround is to right click in a text
input field.


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