Bug 76213 - alternatives: 'Enter to keep the default[*]'
Summary: alternatives: 'Enter to keep the default[*]'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: chkconfig
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
URL:
Whiteboard:
: 77976 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-18 09:04 UTC by Tim Waugh
Modified: 2014-03-17 02:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-01-31 21:12:13 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:332 0 normal SHIPPED_LIVE Updated chkconfig package 2004-08-18 04:00:00 UTC

Description Tim Waugh 2002-10-18 09:04:29 UTC
Description of Problem:
alternatives claims that 'Enter' will use the entry marked '*'; in fact it uses
the entry marked '+'.

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

How Reproducible:
100%

Steps to Reproduce:
1. Install LPRng, cups.
2. alternatives --config print (select cups)
3. alternatives --config print (press enter)
4. alternatives --config print

Actual Results:
The '+' entry is used.

Expected Results:
The message says 'Enter to keep the current selection[+]'.

Comment 1 Jeremy Katz 2003-01-10 07:00:22 UTC
*** Bug 77976 has been marked as a duplicate of this bug. ***

Comment 2 Bill Nottingham 2003-01-31 21:12:13 UTC
Fixed in 1.3.8-1.

Comment 3 John Flanagan 2004-08-18 15:13:13 UTC
An errata 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 the 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.

http://rhn.redhat.com/errata/RHBA-2004-332.html



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