Error with keys in certain rows

[GoogleCodeExporter]

What steps will reproduce the problem?
1.turn on logkeys, it starts normally
2.turn off logkeys by typing "gkeys --kill" results in the following text
3."kofjeya --jikk"; which when you compare the top row letters are getting 
correctly mapped (row starting with q), but second row letters are off by one.

What is the expected output?gkeys --kill
What do you see instead?kofjeya --jikk

What version of the product are you using (`logkeys --help`)?0.1.1a
On what operating system?ubuntu 10.04

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

When I try to open dumpkeys.output with gedit I get an error, can't recognize 
encoding. It then gives me a choice of "Current Locale (UTF-8)" and "Western 
(ISO-8859-15)", The Current Locale does not work, but the Western does for 
correctly opening the file.

Also, I am on an HP laptop (pavillion)

Original issue reported on code.google.com by markITman2@gmail.com on 9 Jun 2010 at 6:09

Attachments:

• dumpkeys.output

[GoogleCodeExporter]

I could not submit my bug report while I had files attached. Will try and add 
later.

Original comment by markITman2@gmail.com on 9 Jun 2010 at 6:10

[GoogleCodeExporter]

trying to add files.....

Original comment by markITman2@gmail.com on 9 Jun 2010 at 6:10

Attachments:

• dumpkeys.output

[GoogleCodeExporter]

next file.....

Original comment by markITman2@gmail.com on 9 Jun 2010 at 6:12

Attachments:

• my_lang.map

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

kaue.mendez,

can you please submit your 
`dumpkeys -n > dumpkeys.out` and `logkeys --export-keymap=out.map` too?

I remember checking, but I couldn't figure out why it goes wrong. :$

I will look at it again, but if anybody has anything to chip in, please feel 
free to. :)

Original comment by kernc...@gmail.com on 25 Jul 2010 at 4:40

• Changed state: NeedMoreInfo

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

having exact same issue, using a microsft comfort wave keyboard on a compaq 
desktop

Original comment by TickleMe...@gmail.com on 8 Aug 2010 at 2:34

[GoogleCodeExporter]

I am having the same issue. 1st row works fine. 2nd row are off by 1, and 3rd 
row are off by 2. 

Using Ubuntu 10.04

Original comment by Rodro.Br...@gmail.com on 19 Aug 2010 at 7:06

[GoogleCodeExporter]

Same issue. Ubuntu 10.04 64bit
Keyboard layout USA Generic 104-key PC
Language LANG=en_CA.utf8 - LC_CTYPE="en_CA.utf8"

Attaching files for /proc/bus/input/devices, dumpkeys.output, my_lang.map

Original comment by tyb...@hotmail.com on 18 Sep 2010 at 8:22

Attachments:

• devices
• dumpkeys.output
• my_lang.map

[GoogleCodeExporter]

Thanks.

For the time being, if it suits you (i.e. keys look right), run logkeys with -u 
switch.

Original comment by kernc...@gmail.com on 18 Sep 2010 at 8:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Also on a HP Elitebook and having the same problem.
but 

my top row is shifted 2 keys
and second \ third row is shifted 3 keys

Original comment by brain...@gmail.com on 27 Oct 2010 at 4:31

Attachments:

• out.txt
• dumpkeys.out

[GoogleCodeExporter]

TO ALL THOSE WHO ARE HAVING THIS ISSUE

As the project lead said use -u switch, that is

sudo logkeys -u --start

Bingo !

Just to try >>

$touch test.log
$sudo logkeys -u --start --output test.log

on another terminal window, try

$tail --follow test.log

I hope the problem is solved. I had the same prob, but now it's alll fixed xD

Kudos to the developer!

Original comment by roy.zyo on 14 Nov 2010 at 8:10

[GoogleCodeExporter]

have tried with -u and with --output FILE and am still experiencing the same 
error.

Original comment by brain...@gmail.com on 23 Dec 2010 at 9:14

[GoogleCodeExporter]

I had the same issue as kernc...@gmail.com 
> I am having the same issue. 
> 1st row works fine. 2nd row are off by 1, and 3rd row are off by 2

Solution:
1) Create a fresh keymap:

sudo logkeys --export-keymap mykeymap.txt

2) Start to modify the keymap

vim mykeymap.txt

3) Find the following lines:

<code>
<LCtrl>
܂
a A
s S
d D
f F
g G
h H
j J
k K
l L
; : ;
'
<LShft>
` ~
܀
\ |
z Z
x X
c C
v V
b B
n N
m M
, < ,
<RShft>
</code>

4) Remove the line directly following <LCtrl> (with comma-like thingy) and put 
it back before <LShft>. The number of lines between <LCtrl> and <LShft> remains 
the same

5) Remove the two lines directly following <LShft> (with squiggle and 
cross-like thingy) and put these back before <LShft>. The number of lines 
between <LCtrl> and <RShft> remains the same

6) The keymap is repaired now. Call logkeys with this keymap:

sudo logkeys -s -o mylogfile.txt -m mykeymap.txt

Original comment by richelbi...@gmail.com on 21 Mar 2013 at 6:28

Attachments:

• mykeymap.txt
• mykeymap_old.txt

[GoogleCodeExporter]

working fine with all keys including (~`?/) which are not working in previous 
solution by richelbi...@gmail.com

Original comment by rickycha...@gmail.com on 26 Aug 2013 at 11:41

Attachments:

• mykeymap.txt