Bug 89211 - loadkeys is inoperative -- this does not apply to redhat-keyboard-config but the /bin/loadkeys binary
Summary: loadkeys is inoperative -- this does not apply to redhat-keyboard-config but ...
Keywords:
Status: CLOSED DUPLICATE of bug 90562
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kbd
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Eido Inoue
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-21 02:41 UTC by Need Real Name
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:45 UTC


Attachments (Terms of Use)

Description Need Real Name 2003-04-21 02:41:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When executing the /bin/loadkeys command the keymap is not changed and loadkeys
exits with an error.  It appears to me that there is an extra leading
forward-slash that causes the problem.  See my error message below.

[root@ben root]# old.loadkeys dvorak
Loading //lib/kbd/keymaps/i386/dvorak
input in flex scanner failed

I coppied in the loadkeys binary from my RH8 box and now it works fine.

[root@ben root]# loadkeys dvorak
Loading /lib/kbd/keymaps/i386/dvorak/dvorak.map.gz

PS Sorry to assign this to redhat-config-keyboard.  It's not a good match but
it's the best I could find.

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


How reproducible:
Always

Steps to Reproduce:
1.boot with dvorak as the default keymap
or 
2.issue the loadkeys command

    

Actual Results:  error message showing an extra leading forward slash

Expected Results:  keymap change

Additional info:

Comment 1 Brent Fox 2003-04-21 19:10:08 UTC
I think that kbd is the component you are looking for.

Comment 2 Eido Inoue 2003-07-25 18:58:25 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:52:45 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.