Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#22 no down arrow with keytouch 2.4.0

other
open
nobody
None
5
2008-07-11
2008-07-11
Anonymous
No

I have a Logitech Wave Keyboard (USB) and tried the new keytouch 2.4.0 (and keytouch-editor 3.2.0-beta) to get this USB keyboard working. I compiled it from source with kernel 2.6.25-2-amd64.

All is working fine except the down arrow key. Within xev I don't get KeyPress events anymore (only KeyRelease) for this key. When I kill keytouchd the down arrow key is working ok. Attached the keyboard file.

Thanks in advance. Kind regards,
Theo Fokkinga
t.s.fokkinga@uva.nl

Output of xev with keytouchd running:

KeymapNotify event, serial 28, synthetic NO, window 0x0,
keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 16 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

KeyRelease event, serial 28, synthetic NO, window 0x4c00001,
root 0x13b, subw 0x0, time 20567578, (-1082,497), root:(1933,523),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

Output of xev without keytouchd running:

KeyPress event, serial 28, synthetic NO, window 0x400001,
root 0x13b, subw 0x0, time 20532186, (-1131,571), root:(1884,597),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 31, synthetic NO, window 0x400001,
root 0x13b, subw 0x0, time 20532474, (-1131,571), root:(1884,597),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

Discussion

  • Keyboard file of the Logitech Wave Keyboard (USB)

     
    Attachments
  • Sorry for this late reply.

    Most of the times these kind of problems are caused by a function key that has the same scancode or usb-code as the down key. You can check whether this is the case by checking the scancode or usb-code of the down key that is detected by keytouch-editor.

    What I noticed when checking your keyboard file is that all the scancodes in the file are large numbers (> 255). KeyTouch-editor creates a scancode element in the file if the keyboard was connected via PS/2 and the keys scancode was detected while pressing it. However normally these scancodes have values <= 255, so I am wondering why they are that large in your keyboard file. Did you connect your keyboard via USB and later via PS/2?

    Regards,
    Marvin Raaijmakers

     
  • Please respond or this bug will be closed.