Bug 101185 - Step 3, "Back" button on rhn_register TUI screen doesn't work
Summary: Step 3, "Back" button on rhn_register TUI screen doesn't work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: up2date
Version: 2.1
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks: up2date-rhel2.1-u6
TreeView+ depends on / blocked
 
Reported: 2003-07-29 21:28 UTC by Glen A. Foster
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:24:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Glen A. Foster 2003-07-29 21:28:26 UTC
Description of problem: Running rhn_register in TUI mode, when you get to the
screen entitled "Step 3: Register a System Profile - Hardware", the Back button
doesn't go back to the previous step.

Version-Release number of selected component (if applicable):
# rpm -q rhn_register
rhn_register-2.8.34-1.2.1AS

How reproducible: always (100%)

Steps to Reproduce:
1. Install RHAS2.1 update 2 on an IA64 system
2. run_register
3. ... try to go back on the screen for Step 3

Comment 1 Glen A. Foster 2004-04-28 22:59:18 UTC
Still broken in RHEL2.1 update 4

Comment 2 RHEL Program Management 2007-10-19 19:24:32 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.


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