Bug 452836 - various usability problems of GUI rhn_register
various usability problems of GUI rhn_register
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Sayli Karmarkar
Preethi Thomas
Depends On:
  Show dependency treegraph
Reported: 2008-06-25 08:23 EDT by Jan Hutař
Modified: 2015-03-22 21:09 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-18 16:14:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2008-06-25 08:23:33 EDT
Description of problem:
There are few things that could be improved in rhn_register GUI:
 * back button do not work
 * "Why register?" screen says "Take me *back* so I can provide ..." and then 
to go back you have to press button "Forward"
 * "Forgot your Red Hat login?" tip says you can find it on www.redhat.com/... 
- even when you are using RHN Satellite
 * you can not click on or at least Copy&Paste URLs from the screens
 * "All available updates" option should be above "Limited updates" one
 * why there is a additional warning "Moving to earlier releases won't be 
possible" when I select "All available updates" - am I doing something bad?

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

How reproducible:

Steps to Reproduce:
1. go through rhn_register GUI

Actual results:
see the problems above (section "Description of problem")

Expected results:
no such problems

Additional info:
Somehow related TUI bug 452817
Comment 17 errata-xmlrpc 2009-05-18 16:14:06 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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