[SLE] setkeycodes then xev reports wrong keycode

burgeke_at_HQ.VerizonWireless.com
Date: 09/10/04

  • Next message: burgeke_at_HQ.VerizonWireless.com: "RE: [SLE] setkeycodes then xev reports wrong keycode" 
    To: suse-linux-e@suse.com
Date: Fri, 10 Sep 2004 07:39:30 -0400

    I have a strange problem under SuSE 9.1 trying to use setkeycodes to define
    an unknown key and then using xmodmap to map it to the key I want. Here is
    what I have done:

    setkeycodes e00a 121
    showkey (this verified that the above worked)
    xmodmap -e 'keycode 121 = F21'

    Then I tried to map F21 using KDE's keyboard shortcuts applett in the
    Control Center. It never saw the keypress as F21.

    So I fired up xev to verify the keycode... Turns out it is set to a
    different keycode - 134!

    So in summary, no matter what keycode I set e00a to using setkeycodes, and
    although showkey verifies I set it correctly, X sees the code as a different
    one.

    Is there something I am missing here? The same exact procedure does work in
    Fedora Core 2... I am stumped!

    BTW: I have several unknown keys that have the same problem.

    Regards,
    Keith 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: burgeke_at_HQ.VerizonWireless.com: "RE: [SLE] setkeycodes then xev reports wrong keycode"