Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Linux] KP_ENTER seen as ENTER #94

Closed
leinardi opened this issue Sep 28, 2014 · 2 comments
Closed

[Linux] KP_ENTER seen as ENTER #94

leinardi opened this issue Sep 28, 2014 · 2 comments

Comments

@leinardi
Copy link

I do not know if it is a specific problem of my keyboard (Logitech G15 v2) but CS:GO sees the KP_ENTER key as the ENTER key. The other KP keys work properly.

xev properly recognize the two keys:

KeyPress event, serial 37, synthetic NO, window 0x5c00001,
    root 0x2a9, subw 0x0, time 2499445, (103,-13), root:(1745,39),
    state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
"   XmbLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5c00001,
    root 0x2a9, subw 0x0, time 2499509, (103,-13), root:(1745,39),
    state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x5c00001,
    root 0x2a9, subw 0x0, time 2500885, (103,-13), root:(1745,39),
    state 0x10, keycode 104 (keysym 0xff8d, KP_Enter), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
"   XmbLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5c00001,
    root 0x2a9, subw 0x0, time 2500949, (103,-13), root:(1745,39),
    state 0x10, keycode 104 (keysym 0xff8d, KP_Enter), same_screen YES,
"   XLookupString gives 1 bytes: (0d) "
    XFilterEvent returns: False

I can reproduce the bug by using these binds:

bind "KP_ENTER" "say KP_ENTER"
bind "ENTER" "say ENTER"

My system information

@eRadicant
Copy link

Can confirm is a bug
Not keyboard specific

edit: dupe #51

@leinardi
Copy link
Author

leinardi commented Oct 3, 2014

I apologize, I searched for a similar report but had not found anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants