Bug 190983 - anaconda uses corrupted keymap for layout "German latin1 w/ no dead keys"
Summary: anaconda uses corrupted keymap for layout "German latin1 w/ no dead keys"
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-07 18:24 UTC by Joachim Frieben
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-05-16 14:15:59 UTC

Attachments (Terms of Use)

Description Joachim Frieben 2006-05-07 18:24:25 UTC
Description of problem:
Current "anaconda" uses a corrupted keymap for the layout type
"German latin1 w/ no dead keys".

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

How reproducible:

Steps to Reproduce:
1. Boot system from current "boot.iso".
2. Choose layout "German latin1 w/ no dead keys".
3. Try to enter the http download directory path.
Actual results:
The combination <shift>+number yields wrong results. The slash
character is not accessible via "<shift>+7". Instead a curly
bracket "{" is printed.

Expected results:
Character output should correspond to the keyboard layout.

Additional info:
It is necessary to get back to the keyboard layout selection menu.
The standard US keyboard layout is chosen and works correctly.
After the installation is completed, "system-config-keyboard" is
used to set the layout to "German latin1 w/ no dead keys". Now,
the keymap is correct!

Comment 1 Jeremy Katz 2006-05-07 20:47:41 UTC
Yeah, something has gone wrong with keyboard layout stuff the middle of last
week.  Chris was investigating

Comment 2 Chris Lumens 2006-05-10 15:15:37 UTC
Please try the next build and let us know if this works for you.  Peter's done
some work which fixes the us keymap at least.

Comment 3 Joachim Frieben 2006-05-10 18:14:39 UTC
Still not fixed in "anaconda-". The "us" keyboard layout
never exhibited any problem to me (?). That's why I used it as a
fallback after the german one turned out to be broken.

Comment 4 Chris Lumens 2006-05-10 18:25:41 UTC
No, the next build. is the current one.

Comment 5 Chris Lumens 2006-05-16 14:15:59 UTC
This should now be fixed in

Comment 6 Joachim Frieben 2006-05-16 18:21:05 UTC
Tried today and works as expected. Thanks!

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