Bug 82398 - No way to test selected keyboard layout in Phoebe2's anaconda
Summary: No way to test selected keyboard layout in Phoebe2's anaconda
Status: CLOSED DUPLICATE of bug 81744
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-keyboard (Show other bugs)
(Show other bugs)
Version: 9
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-21 20:43 UTC by Bernd Bartmann
Modified: 2008-01-17 17:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 18:51:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Bernd Bartmann 2003-01-21 20:43:18 UTC
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:
Always

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

Additional info:

Comment 1 Michael Fulbright 2003-01-22 17:50:37 UTC
Anaconda uses the keyboard configuaration component from redhat-config-keyboard now.

Comment 2 Brent Fox 2003-01-22 17:58:07 UTC

*** This bug has been marked as a duplicate of 81744 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:51:17 UTC
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.