Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 1749 - keyboard maps not found correctly
keyboard maps not found correctly
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-03-24 16:02 EST by Michael K. Johnson
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-04-09 14:27:01 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 Michael K. Johnson 1999-03-24 16:02:35 EST
linuxconf appears to look below the base keymap directory
for filenames matching the regexp [a-zA-Z].map.gz
This is now obsolete.  The new way is to do something
functionally equivalent to
find /usr/lib/kbd/keymaps/<arch> | egrep '.k?map'
to get the list of files and
sed 's:.*/\([^/][^/]*\)\.k*map\.gz:\1:g'
to get the names that should be attached to those
Comment 1 Michael K. Johnson 1999-03-31 11:14:59 EST
Jacques, this bug still exists in linuxconf-1.14r2
I still only see default, ro, or sr as options.
Comment 2 Michael K. Johnson 1999-04-08 16:20:59 EDT
Still occurs in linuxconf-1.14r3.1
Comment 3 Michael K. Johnson 1999-04-09 12:33:59 EDT
Still occurs in linuxconf-1.14r4
Jacques, what do I need to do to help you fix this?
Comment 4 Michael K. Johnson 1999-04-09 14:12:59 EDT
Jacques, I found it.  You were only looking for .map and .map.gz
files, not .kmap and .kmap.gz files.  I'll send the patch in email.

------- Email Received From  "Michael K. Johnson" <johnsonm@redhat.com> 04/09/99 14:26 -------
Comment 5 Michael K. Johnson 1999-04-09 14:27:59 EDT
Fixed in linuxconf-1.14r4-2

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