Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 72984

Summary: up2date screen is confusing
Product: [Retired] Red Hat Linux Reporter: Gerald Teschl <gt>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED RAWHIDE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: gafton, mihai.ibanescu, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-02-14 15:05:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 82264    

Description Gerald Teschl 2002-08-29 18:12:27 UTC 
In "Step 2" of the registration wizard the instructions say that if one is
already registered, one should just enter name and password, but it will
not accept "name and password" it requires all four fields to be filled out.
This is confusing.
Comment 1 Adrian Likins 2002-08-31 08:47:22 UTC 
Hmm, indeed. This is long standing ui bug.

Hope to get it fixed, but glade issues seem to
be causing problems.
Comment 2 Joe Orton 2002-09-04 14:22:30 UTC 
In fact the UI does not mention that the e-mail address is required, for either
a new user or an existing user:

"Yes: Enter your current user name and password below."
"No: Choose a new user name and password and enter it below."

I am confused by this dialog every time I'm confronted by it, until I realise
that the e-mail address is in fact required.

Another confusing aspect of this UI is that if you enter an incorrect password,
you're prompted with a dialog which says "This username is already taken.".
Comment 3 Adrian Likins 2003-01-28 00:38:21 UTC 
this should be improved somewhat in version 3.1.5 or higher....
Comment 4 Jay Turner 2003-02-14 15:05:47 UTC 
Fix confirmed with up2date-3.1.15-7.