Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 70369 - duplicate keyboard layouts in anaconda keyboard selection screen
duplicate keyboard layouts in anaconda keyboard selection screen
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
Blocks: 67218
  Show dependency treegraph
Reported: 2002-07-31 16:44 EDT by Geert Noel
Modified: 2007-04-18 12:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-02 16:03:52 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 Geert Noel 2002-07-31 16:44:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724

Description of problem:
For example: there is a be-latin and be-latin2 keyboard for Belgium. If I
remember correctly there was only one Belgian keyboard in the previous Red Hat
releases. How does one know which one of the two should be selected (especially
now the test field has disappeared)? Probably be-latin, cuz if I chose the
be-latin2 layout it failed to load during bootup.

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

How reproducible:

Steps to Reproduce:
1. install limbo2
2. the keyboard selection screen lists some countries twice
3. choose be-latin2 and it fails to load during first boot

Additional info:
Comment 1 Michael Fulbright 2002-08-02 12:16:36 EDT
Brent any ideas?
Comment 2 Jeremy Katz 2002-08-02 16:03:46 EDT
be-latin1 is the correct one with kbd; I've removed the duplicate in CVS
Comment 3 Brent Fox 2002-08-02 16:11:41 EDT
Ok, since the be-latin2 keyboard has been removed from the list, I'm going to
close this bug now.  Thanks for your report.

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