I am trying to show keyboard event by app xinput. I tried on three workstations. On the first two workstations (in local X-session), all is good:

Get device list:

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜  ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜  ↳ HID 1241:1177 id=8 [slave pointer (2)]
⎜  ↳ SIGMACH1P USB Keykoard id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
   ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
   ↳ Power Button id=6 [slave keyboard (3)]
   ↳ Power Button id=7 [slave keyboard (3)]
   ↳ SIGMACH1P USB Keykoard id=9 [slave keyboard (3)]

Device event:

$ xinput test 9
key release 36
key press 48
key press 47
key release 48
key press 46
lkey release 47
key release 46
key press 41
key press 36
key release 41
key release 36
key press 62
key release 62
key press 37

But on the third workstation, I connect from X-terminal x2go (connect from Windows 7). And in this workstation xinput does not fulfill its function. Xinput does not find devices and segfaults.

$ xinput
"pointer"   id=0    [XPointer]
"keyboard"  id=1    [XKeyboard]

$ xinput test 1
unable to find device '1'

$ xinput test-xi2 1
"keyboard"  id=1    [XKeyboard]
    Num_keys is 248
    Min_keycode is 8
    Max_keycode is 255
Segmentation fault

Question 1: The xinput principial does not work if connection to X-server stable from X-terminal? Or it is bug in standart X11 application?

Question 2: How to alternative get global keyboard event (push and release key) if connect from X-terminal (x2go)?

From connect: Windows 7 Pro, official X2GO client from site x2go.org.
To connect: Debian 7.8, LXDE, official server X2GO from site x2go.org.

1 Answer 1


The segmentation fault is a bug in the xinput program.

The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .