2018-03-07, 10:34
(2018-03-04, 12:28)dantist Wrote:(2018-03-04, 07:05)loggio Wrote: I can confirm longpress keys are not working.Maybe this is also related to my FLIRC issue with scrolling too quickly through menu entries ?
this is true for all long presses, using Bluetooth keyboard or a Flirc.
I need to get you guys to tell me what key isn't mapped. You have to do this via command line in an ssh session.
you can either use the following command
Code:
libinput list-devices
which will output something like
Code:
Device: flirc.tv flirc
Kernel: /dev/input/event16
Group: 6
Seat: seat0, default
Capabilities: keyboard pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: disabled
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
then please record the events like so
Code:
libinput debug-events --device /dev/input/event16
then press the keys (both regular and long press). the output will look like so:
Code:
-event16 DEVICE_ADDED flirc.tv flirc seat0 default group1 cap:kp scroll-nat
event16 KEYBOARD_KEY +2.74s KEY_UP (103) pressed
event16 KEYBOARD_KEY +2.77s KEY_UP (103) released
event16 KEYBOARD_KEY +4.66s KEY_VOLUMEUP (115) pressed
event16 KEYBOARD_KEY +4.69s KEY_VOLUMEUP (115) released
if libinput command isn't included you can do something similar with evtest which is included in the system-tools add-on.