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

Most Keys Log Accurately - Some Keys Are Broken! :/ #162

Open
ultrablast opened this issue Jan 7, 2017 · 7 comments

Comments

Projects
None yet
4 participants
@ultrablast
Copy link

commented Jan 7, 2017

Hi Folks. If I placed this request in the wrong area, my apologies. Please re-direct to the right area if necessary. I borrowed one of the earlier posts as a template to provide the data necessary to help repair keymappings that aren't working correctly on a newer model DELL Ultrabook laptop.

What steps will reproduce the problem?

  1. Start Logkeys (and kill logkeys as needed) No problems there!
  2. Type something I would expect to properly translate in the .log but the keymapping seems to be incorrect. (Best guess so far!)
  3. Scrambled output in the "github.log.txt" file output from logkeys.
  4. Ask the experts!

What is the expected output? >> Just typing something for github to help with!
What do you see instead? >> Huat typibf aonetgif dor fitguv to gekp witg!
github.log.txt

What version of the product are you using? >> 0.1.1b-svn
On what operating system? >> Ubuntu 16.04

Please provide any additional information below.
Attach contents of /proc/bus/input/devices >>DONE<<
devices.txt

Include the output of command dumpkeys -n > dumpkeys.output >>DONE<<
dumpkeys.output.txt

I have no problem reading the dumpkeys.output in gedit.

Let me know if I need to provide anything else to help troubleshoot this situation.
Anything helps!

Warm Regards

@ultrablast

This comment has been minimized.

Copy link
Author

commented Jan 14, 2017

Anybody out there? lol

@Gremlyn

This comment has been minimized.

Copy link

commented Jan 18, 2017

I am seeing the same thing, also on Ubuntu 16.04.

dumpkeys.output.txt
devices.txt

@kernc

This comment has been minimized.

Copy link
Owner

commented Jan 23, 2017

I reckon logkeys was originally coded for a pc105 laid out keyboard and it may not support pc104 (or other) keyboards without some rewriting. If you're using en_US layout, have you tried -u switch?

@Gremlyn

This comment has been minimized.

Copy link

commented Jan 23, 2017

I had not tried it, but just did and no change.

@PeterAndreus

This comment has been minimized.

Copy link

commented Jan 27, 2017

I had same problem. Try use -m switch with en_US_ubuntu_1204.map stored in logkeys-master/keymaps

logkeys -s -o log.log -m logkeys-master/keymaps/en_US_ubuntu_1204.map

@ultrablast

This comment has been minimized.

Copy link
Author

commented Jan 29, 2017

First off, I wanted to send a kind thank you to everyone who took time to help with this case.

@kernc - I did try with the -u switch, but it did not seem to matter. Keys logged were still incorrect.

@PeterAndreus - I was able to find and download the en_US_ubuntu_1204.map file and unfortunately it did not work. Here is the result I received (error) when I tried it:

logkeys -s -o log.log -m /home/bench/Desktop/en_US_ubuntu_1204.map

logkeys:/home/bench/Desktop/en_US_ubuntu_1204.map:1: No characters on line
Segmentation fault (core dumped)

Ubuntu offered to send an error report, but I declined.

Any other tips? Seems like we may be getting warmer!

Thanks again & Cheers,
-Ultrablast

@PeterAndreus

This comment has been minimized.

Copy link

commented Jan 29, 2017

@ultrablast i had mine en_US_ubuntu_1204.map right in downloaded version. which version do you have?
mine: logkeys version: 0.1.1b-svn
after download from git i run autogen.sh according to INSTALL file before compiling logkeys.
Did you do same steps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.