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 82398 - No way to test selected keyboard layout in Phoebe2's anaconda
No way to test selected keyboard layout in Phoebe2's anaconda
Status: CLOSED DUPLICATE of bug 81744
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-keyboard (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-01-21 15:43 EST by Bernd Bartmann
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:17 EST
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 Bernd Bartmann 2003-01-21 15:43:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
In earlier anaconda versions it was possible to test the selected keyboard
layout in a small text input field. This is no longer available. As there is
this the (at least for me pointless) choice between de-latin1 and
de-latin1-nodeadkeys it would be good if Joe User could test his keyboard
layout. The other alternative would be to just remove the choice between
de-latin1 and de-latin1-nodeadkeys and just use de-latin1-nodeadkeys. Joe User
will never even know what "dead" keys are!

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

How reproducible:

Steps to Reproduce:
1. Try to test your keyboard layout

Additional info:
Comment 1 Michael Fulbright 2003-01-22 12:50:37 EST
Anaconda uses the keyboard configuaration component from redhat-config-keyboard now.
Comment 2 Brent Fox 2003-01-22 12:58:07 EST

*** This bug has been marked as a duplicate of 81744 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:17 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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