[doug]

@doug try stoping kodi first

Code:

systemctl stop kodi

Okay, now there are events recorded... 

Code:

Kodi-FR:~ # libinput-list-devices
Device:           flirc.tv flirc
Kernel:           /dev/input/event0
Group:            1
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

Here is the Enter key with a normal press and then a long press.

Code:

Kodi-FR:~/.update # libinput-debug-events --device /dev/input/event0
-event0 DEVICE_ADDED flirc.tv flirc seat0 default group1 cap:kp scroll-nat
event0 KEYBOARD_KEY +2.11s *** (-1) pressed
event0 KEYBOARD_KEY +2.30s *** (-1) released
event0 KEYBOARD_KEY +3.14s *** (-1) pressed
event0 KEYBOARD_KEY +4.83s *** (-1) released

I didn't include them above, but there are several keypresses (skip back, skip forward, ffd, rwd, stop, menu/guide, back ) that generate the exact same generic "*** (-1)" event output. Other keys generate unique events such as "KEY_UP (103)". My keys that generate unique events include, up, down, left right, play/pause, ctrl-F11, ctrl-F12.

Edit: the ctrl-F11 and ctrl-F12 are odd. They generate:

Code:

event0   KEYBOARD_KEY     +722.88s     *** (-1) pressed
 event0   KEYBOARD_KEY     +722.88s     KEY_F11 (87) pressed
 event0   KEYBOARD_KEY     +723.07s     *** (-1) released
 event0   KEYBOARD_KEY     +723.07s     KEY_F11 (87) released

So it appears the ctrl isn't uniquely identified.  I use the ctrl-XX kepresses with python scripts to change inputs, power on/off, etc. The scripts still run fine with the libinput changes.