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

Keymapping issue #245

Open
za3k opened this issue Aug 4, 2022 · 1 comment · May be fixed by #246
Open

Keymapping issue #245

za3k opened this issue Aug 4, 2022 · 1 comment · May be fixed by #246

Comments

@za3k
Copy link

za3k commented Aug 4, 2022

It looks like something odd is going on with keymaps. On two computers, I run:

 sudo logkeys -s -u --no-daemon

I add keycode logging by adding a printf in update_key_state at the top of the default case.

On both, I press the "1" button. On both computers, keycode 2 is registered, which matches what I expect from ex. https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h. On both, I see /var/log/logkeys.log log key 2 as being pressed (incorrect).

On both, I press the "q" button. On both computers, keycode 16 is registered.
One one computer, w is logged to the file. On the other, q is logged to the file.

In short, they don't seem to be using the same keymap, even though -u is passed.

@za3k
Copy link
Author

za3k commented Aug 4, 2022

Tracking it down further, the -u option is not used except together with --export-keymap. The code simply ignores it.

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

Successfully merging a pull request may close this issue.

1 participant