#781532 x2x: All key events received as keycode 204 (NoSymbol)

Package:
x2x
Source:
x2x
Description:
Link two X displays together, simulating a multiheaded display
Submitter:
Greg Wooledge
Date:
2017-11-12 21:57:06 UTC
Severity:
normal
#781532#5
Date:
2015-03-30 16:26:50 UTC
From:
To:
I have been using x2x between my HP-UX workstation and my dual-boot
Debian box for a while.  Today I upgraded to jessie, and x2x keyboard
events stopped working entirely.  Some Google searches led me to this
page, which describes the problem in the upstream bug tracker:

https://github.com/dottedmag/x2x/issues/9

I have the same symptom described in that bug: all key events sent
from the HP-UX workstation's keyboard are received as keycode 204
(NoSymbol) on the Debian system running x2x, as confirmed by xev.

Here is my exact invocation from the HP-UX workstation:

ssh -f -X wooledg x2x -west -to :0 -resurface

where "wooledg" is the Debian system's hostname.
#781532#10
Date:
2015-03-30 17:22:02 UTC
From:
To:
FYI, the one-line patch suggested in the upstream bug report does NOT
work for me.  It makes key events come across, but as the wrong keys.
E.g. pressing 'z' on the HP-UX keyboard makes ']' appear on the Debian
terminal, Ctrl makes 'e' appear and so on.
#781532#15
Date:
2017-03-13 12:41:32 UTC
From:
To:
FYI, the problem (all keyboard events received as NoSymbol) continues
for me in the stretch version of x2x (1.30-3).

Reinstalling my x2x_1.27.svn.20060501-4_amd64.deb package (and putting it
on hold) continues to be my only known workaround.
#781532#20
Date:
2017-11-12 21:34:29 UTC
From:
To:
I also confirm the bug. Checking keycodes sent/received with ev, I get
that a keycode 11 or 12 sent with the 'to' keyboard are seen as
keycode 77 on the 'from' desktop. Letter keys (a-z) usually work fine,
but 1-9 are totally messed up.

Both to and from machines run Debian stretch with amd64 arch.

Greetings,
#781532#25
Date:
2017-11-12 21:52:11 UTC
From:
To:
skimming through the manpage, I found out this trick:

       If you have trouble with some keys not working, try setting the keymaps
       on both systems to be the same using setxkbmap.

That actually solved my issue, in my case having the same:

$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     be,es,jp

on both machines.