Created attachment 95290 [details] Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser During system startup, I get these kind of messages with systemd-210 (Arch Linux x86_64) Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Error calling EVIOCSKEYCODE (scan code 0xc0183, key code 226): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1005, key code 212): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc101f, key code 419): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1020, key code 418): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1041, key code 421): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1042, key code 423): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1043, key code 397): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1044, key code 149): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1045, key code 202): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1046, key code 203): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc1048, key code 430): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc104a, key code 136): Invalid argument Error calling EVIOCSKEYCODE (scan code 0xc104c, key code 162): Invalid argument If I can provide some more information to debug this, please let me know. Thanks.
That's hwdb trying to apply keyboard-fixups to your device. hwdb tells me, this is supposed to be for "Logitech Wave cordless", however, your device is definitely a different one. Good thing is, you can safely ignore these errors. But I'd still like to figure out where this entry comes from. I'm adding Martin Pitt as he added the code. @Martin: It says "Wave cordless" two times in hwdb/60-keyboard.hwdb. Are you sure the second entry is a positive match? According to this report, 046d:c516 is the LX710, which is a different device than the Wave-cordless.
Thanks. The exact model of my keyboard/mouse combo is Logitech EX100
I confirm this also happens with Logitech EX110 cordless keyboard/mouse usb combo.
In my case: [ 0.624474] systemd-udevd[104]: starting version 204 [ 15.248378] systemd-udevd[335]: starting version 204 [ 15.756714] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756743] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756758] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756773] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756787] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756802] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756817] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756831] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756846] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756860] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756875] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756898] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument [ 15.756922] systemd-udevd[360]: Error calling EVIOCSKEYCODE: Invalid argument
These were translated from the original udev rules, which were ENV{ID_VENDOR}=="Logitech*", ATTRS{name}=="Logitech USB Multimedia Keyboard", RUN+="keymap $name logitech-wave" ENV{ID_VENDOR}=="Logitech*", ATTRS{name}=="Logitech USB Receiver", RUN+="keymap $name logitech-wave-cordless" Since hwdb doesn't support his kind of matches, I used http://www.linux-usb.org/usb.ids to look up the corresponding product IDs. Both C317 and C517 exist as keyboards, and Gerardo confirmed that this is a keyboard/mouse combo. So supposedly this USB device hasa two different interfaces, and the setkeycode is applied to the wrong one. Gerardo/David, do all of the special keys (zoom in/out, media, wordprocessor, calendar, etc.) actually work? (In the sense of opening the corresponding programs, or at least giving proper keycode names in "evtest")? Can you please do udevadm info --export-db > /tmp/udev.txt and attach /tmp/udev.txt here? That will give more insight than the lspci dump. Thanks!
(In reply to comment #5) > Gerardo/David, do all of the special keys (zoom in/out, media, > wordprocessor, calendar, etc.) actually work? (In the sense of opening the > corresponding programs, or at least giving proper keycode names in "evtest")? At least inside KDE, running evtest as root, there is no output relevant to these keys (located at F1-F12 keys). Volume keys works on KDE (located at Right/Left arrow) and Mute (down Arrow), but nothing is shows on evtest about this event. Note that normal keys are reported by evtest. > > Can you please do > > udevadm info --export-db > /tmp/udev.txt > > and attach /tmp/udev.txt here? That will give more insight than the lspci > dump. > Just attaching output of relevant device input (keyboard/mouse). > Thanks! Thanks you.
Created attachment 105363 [details] udev db of EX100 combo
Ah, thanks. So apparently interface 00 is the keyboard, interface 01 is the mouse. Can you please try to modify /lib/udev/hwdb.d/60-keyboard.hwdb like this: --- a/hwdb/60-keyboard.hwdb +++ b/hwdb/60-keyboard.hwdb @@ -648,7 +648,7 @@ keyboard:usb:v046DpC317* KEYBOARD_KEY_9004c=ejectclosecd # Wave cordless -keyboard:usb:v046DpC517* +keyboard:usb:v046DpC517*dc*dsc*dp*ic*isc*ip*in00* KEYBOARD_KEY_c101f=zoomout KEYBOARD_KEY_c1020=zoomin KEYBOARD_KEY_c1005=camera I. e. extend the "keyboard:" line like above in the "Wave cordless" stanza that applies to C517 (*not* C317). Then call "sudo udevadm hwdb --update", and either unplug/replug the keyboard, or just reboot. Ideally the magic keys would now work, and the warnings be gone?
(In reply to comment #8) > Ah, thanks. So apparently interface 00 is the keyboard, interface 01 is the > mouse. Can you please try to modify /lib/udev/hwdb.d/60-keyboard.hwdb like > this: > > --- a/hwdb/60-keyboard.hwdb > +++ b/hwdb/60-keyboard.hwdb > @@ -648,7 +648,7 @@ keyboard:usb:v046DpC317* > KEYBOARD_KEY_9004c=ejectclosecd > > # Wave cordless > -keyboard:usb:v046DpC517* > +keyboard:usb:v046DpC517*dc*dsc*dp*ic*isc*ip*in00* > KEYBOARD_KEY_c101f=zoomout > KEYBOARD_KEY_c1020=zoomin > KEYBOARD_KEY_c1005=camera > > > I. e. extend the "keyboard:" line like above in the "Wave cordless" stanza > that applies to C517 (*not* C317). Then call "sudo udevadm hwdb --update", > and either unplug/replug the keyboard, or just reboot. Ideally the magic > keys would now work, and the warnings be gone? OK I updated the text file and binary db. The error in log still persist. Special keys are still not reported in evtest (inside or outside Xorg). Note that these keys are trigger with a FN-key + (F1-F12 | Print | Pause | Arrow-{L,D,R}) in my case.
I did another tests. With or without this patch, the behavior is the same: All FN-keys except (F2) are "detected" by KDE (i.e. trying to assign as hotkeys) The only two FN-key detected by evtest is FN+PRINT (reported as KEY_COMPOSE) and FN-PAUSE (reported as KEY_SCROLLLOCK)
Created attachment 105401 [details] output of evtest
Ah, thanks. Kay, is that rule doing anything wrong here? I. e. should keyboard:usb:v046DpC517*dc*dsc*dp*ic*isc*ip*in00* work and select that particular interface? or does the keymap builtin not support interfaces?
I've Logitech Internet Navigator Keyboard and I'm getting these errors in journal: Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc0201, key code 181): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc0207, key code 234): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc0208, key code 210): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc021a, key code 131): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc0279, key code 182): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc0289, key code 232): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc028b, key code 233): Invalid argument Error calling EVIOCSKEYCODE on device node '/dev/input/event5' (scan code 0xc028c, key code 231): Invalid argument I've only one keyboard but under evtest there are 2 entries: /dev/input/event5: Logitech Logitech USB Keyboard /dev/input/event6: Logitech Logitech USB Keyboard from lsusb Bus 006 Device 004: ID 046d:c309 Logitech, Inc. Internet Keyboard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc309 Internet Keyboard bcdDevice 15.00 iManufacturer 1 Logitech iProduct 2 Logitech USB Keyboard iSerial 0 First one event5 is only regular keys withuot any multimedia keys, they don't work there Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x46d product 0xc309 version 0x110 Input device name: "Logitech Logitech USB Keyboard" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 12 (KEY_MINUS) Event code 13 (KEY_EQUAL) Event code 14 (KEY_BACKSPACE) Event code 15 (KEY_TAB) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 26 (KEY_LEFTBRACE) Event code 27 (KEY_RIGHTBRACE) Event code 28 (KEY_ENTER) Event code 29 (KEY_LEFTCTRL) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 40 (KEY_APOSTROPHE) Event code 41 (KEY_GRAVE) Event code 42 (KEY_LEFTSHIFT) Event code 43 (KEY_BACKSLASH) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 54 (KEY_RIGHTSHIFT) Event code 55 (KEY_KPASTERISK) Event code 56 (KEY_LEFTALT) Event code 57 (KEY_SPACE) Event code 58 (KEY_CAPSLOCK) Event code 59 (KEY_F1) Event code 60 (KEY_F2) Event code 61 (KEY_F3) Event code 62 (KEY_F4) Event code 63 (KEY_F5) Event code 64 (KEY_F6) Event code 65 (KEY_F7) Event code 66 (KEY_F8) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 69 (KEY_NUMLOCK) Event code 70 (KEY_SCROLLLOCK) Event code 71 (KEY_KP7) Event code 72 (KEY_KP8) Event code 73 (KEY_KP9) Event code 74 (KEY_KPMINUS) Event code 75 (KEY_KP4) Event code 76 (KEY_KP5) Event code 77 (KEY_KP6) Event code 78 (KEY_KPPLUS) Event code 79 (KEY_KP1) Event code 80 (KEY_KP2) Event code 81 (KEY_KP3) Event code 82 (KEY_KP0) Event code 83 (KEY_KPDOT) Event code 85 (KEY_ZENKAKUHANKAKU) Event code 86 (KEY_102ND) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 89 (KEY_RO) Event code 90 (KEY_KATAKANA) Event code 91 (KEY_HIRAGANA) Event code 92 (KEY_HENKAN) Event code 93 (KEY_KATAKANAHIRAGANA) Event code 94 (KEY_MUHENKAN) Event code 95 (KEY_KPJPCOMMA) Event code 96 (KEY_KPENTER) Event code 97 (KEY_RIGHTCTRL) Event code 98 (KEY_KPSLASH) Event code 99 (KEY_SYSRQ) Event code 100 (KEY_RIGHTALT) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 110 (KEY_INSERT) Event code 111 (KEY_DELETE) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 117 (KEY_KPEQUAL) Event code 119 (KEY_PAUSE) Event code 121 (KEY_KPCOMMA) Event code 122 (KEY_HANGUEL) Event code 123 (KEY_HANJA) Event code 124 (KEY_YEN) Event code 125 (KEY_LEFTMETA) Event code 126 (KEY_RIGHTMETA) Event code 127 (KEY_COMPOSE) Event code 128 (KEY_STOP) Event code 129 (KEY_AGAIN) Event code 130 (KEY_PROPS) Event code 131 (KEY_UNDO) Event code 132 (KEY_FRONT) Event code 133 (KEY_COPY) Event code 134 (KEY_OPEN) Event code 135 (KEY_PASTE) Event code 136 (KEY_FIND) Event code 137 (KEY_CUT) Event code 138 (KEY_HELP) Event code 183 (KEY_F13) Event code 184 (KEY_F14) Event code 185 (KEY_F15) Event code 186 (KEY_F16) Event code 187 (KEY_F17) Event code 188 (KEY_F18) Event code 189 (KEY_F19) Event code 190 (KEY_F20) Event code 191 (KEY_F21) Event code 192 (KEY_F22) Event code 193 (KEY_F23) Event code 194 (KEY_F24) Event code 240 (KEY_UNKNOWN) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Event type 17 (EV_LED) Event code 0 (LED_NUML) Event code 1 (LED_CAPSL) Event code 2 (LED_SCROLLL) Event code 3 (LED_COMPOSE) Event code 4 (LED_KANA) Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value 250 Repeat code 1 (REP_PERIOD) Value 33 Other is event6 where myltimedia keys works but not others Input device ID: bus 0x3 vendor 0x46d product 0xc309 version 0x110 Input device name: "Logitech Logitech USB Keyboard" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 131 (KEY_UNDO) Event code 140 (KEY_CALC) Event code 142 (KEY_SLEEP) Event code 143 (KEY_WAKEUP) Event code 144 (KEY_FILE) Event code 148 (KEY_PROG1) Event code 155 (KEY_MAIL) Event code 156 (KEY_BOOKMARKS) Event code 158 (KEY_BACK) Event code 159 (KEY_FORWARD) Event code 163 (KEY_NEXTSONG) Event code 164 (KEY_PLAYPAUSE) Event code 165 (KEY_PREVIOUSSONG) Event code 166 (KEY_STOPCD) Event code 171 (KEY_CONFIG) Event code 172 (KEY_HOMEPAGE) Event code 181 (KEY_NEW) Event code 182 (KEY_REDO) Event code 210 (KEY_PRINT) Event code 212 (KEY_CAMERA) Event code 213 (KEY_SOUND) Event code 216 (KEY_CHAT) Event code 217 (KEY_SEARCH) Event code 221 (KEY_SHOP) Event code 231 (KEY_SEND) Event code 232 (KEY_REPLY) Event code 233 (KEY_FORWARDMAIL) Event code 234 (KEY_SAVE) Event code 235 (KEY_DOCUMENTS) Event code 260 (BTN_4) Event code 261 (BTN_5) Event code 262 (BTN_6) Event code 263 (BTN_7) Event code 264 (BTN_8) Event code 265 (BTN_9) Event code 266 (?) Event code 267 (?) Event code 268 (?) Event code 269 (?) Event code 270 (?) Event code 271 (?) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 274 (BTN_MIDDLE) Event code 275 (BTN_SIDE) Event code 276 (BTN_EXTRA) Event code 277 (BTN_FORWARD) Event code 278 (BTN_BACK) Event code 279 (BTN_TASK) Event code 280 (?) Event code 281 (?) Event code 282 (?) Event code 283 (?) Event code 284 (?) Event code 285 (?) Event code 286 (?) Event code 287 (?) Event code 288 (BTN_TRIGGER) Event code 289 (BTN_THUMB) Event code 290 (BTN_THUMB2) Event code 291 (BTN_TOP) Event code 292 (BTN_TOP2) Event code 293 (BTN_PINKIE) Event code 294 (BTN_BASE) Event code 295 (BTN_BASE2) Event code 296 (BTN_BASE3) Event code 297 (BTN_BASE4) Event code 298 (BTN_BASE5) Event code 299 (BTN_BASE6) Event code 300 (?) Event code 301 (?) Event code 302 (?) Event code 303 (BTN_DEAD) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 306 (BTN_C) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 309 (BTN_Z) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event code 319 (?) Event code 442 (?) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Event code 8 (REL_WHEEL) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Seems it should use EVIOCSKEYCODE only for event5 but not event6 udevadm info /dev/input/event5 P: /devices/pci0000:00/0000:00:13.2/usb6/6-4/6-4.2/6-4.2:1.0/0003:046D:C309.0004/input/input6/event5 N: input/event5 S: input/by-id/usb-Logitech_Logitech_USB_Keyboard-event-kbd S: input/by-path/pci-0000:00:13.2-usb-0:4.2:1.0-event-kbd E: DEVLINKS=/dev/input/by-path/pci-0000:00:13.2-usb-0:4.2:1.0-event-kbd /dev/input/by-id/usb-Logitech_Logitech_USB_Keyboard-event-kbd E: DEVNAME=/dev/input/event5 E: DEVPATH=/devices/pci0000:00/0000:00:13.2/usb6/6-4/6-4.2/6-4.2:1.0/0003:046D:C309.0004/input/input6/event5 E: ID_BUS=usb E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_MODEL=Logitech_USB_Keyboard E: ID_MODEL_ENC=Logitech\x20USB\x20Keyboard E: ID_MODEL_ID=c309 E: ID_PATH=pci-0000:00:13.2-usb-0:4.2:1.0 E: ID_PATH_TAG=pci-0000_00_13_2-usb-0_4_2_1_0 E: ID_REVISION=1500 E: ID_SERIAL=Logitech_Logitech_USB_Keyboard E: ID_TYPE=hid E: ID_USB_DRIVER=usbhid E: ID_USB_INTERFACES=:030101:030000: E: ID_USB_INTERFACE_NUM=00 E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: KEYBOARD_KEY_90001=chat E: KEYBOARD_KEY_90002=camera E: KEYBOARD_KEY_90003=prog1 E: KEYBOARD_KEY_90004=shop E: KEYBOARD_KEY_C0194=file E: KEYBOARD_KEY_C01A7=documents E: KEYBOARD_KEY_C01B6=images E: KEYBOARD_KEY_C01B7=sound E: KEYBOARD_KEY_C0201=new E: KEYBOARD_KEY_C0207=save E: KEYBOARD_KEY_C0208=print E: KEYBOARD_KEY_C021A=undo E: KEYBOARD_KEY_C0279=redo E: KEYBOARD_KEY_C0289=reply E: KEYBOARD_KEY_C028B=forwardmail E: KEYBOARD_KEY_C028C=send E: LIBINPUT_DEVICE_GROUP=usb-0000:00:13.2-4 E: MAJOR=13 E: MINOR=69 E: SUBSYSTEM=input E: USEC_INITIALIZED=28408723 udevadm info /dev/input/event6 P: /devices/pci0000:00/0000:00:13.2/usb6/6-4/6-4.2/6-4.2:1.1/0003:046D:C309.0005/input/input7/event6 N: input/event6 S: input/by-id/usb-Logitech_Logitech_USB_Keyboard-if01-event-mouse S: input/by-path/pci-0000:00:13.2-usb-0:4.2:1.1-event-mouse E: DEVLINKS=/dev/input/by-id/usb-Logitech_Logitech_USB_Keyboard-if01-event-mouse /dev/input/by-path/pci-0000:00:13.2-usb-0:4.2:1.1-event-mouse E: DEVNAME=/dev/input/event6 E: DEVPATH=/devices/pci0000:00/0000:00:13.2/usb6/6-4/6-4.2/6-4.2:1.1/0003:046D:C309.0005/input/input7/event6 E: ID_BUS=usb E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_MOUSE=1 E: ID_MODEL=Logitech_USB_Keyboard E: ID_MODEL_ENC=Logitech\x20USB\x20Keyboard E: ID_MODEL_ID=c309 E: ID_PATH=pci-0000:00:13.2-usb-0:4.2:1.1 E: ID_PATH_TAG=pci-0000_00_13_2-usb-0_4_2_1_1 E: ID_REVISION=1500 E: ID_SERIAL=Logitech_Logitech_USB_Keyboard E: ID_TYPE=hid E: ID_USB_DRIVER=usbhid E: ID_USB_INTERFACES=:030101:030000: E: ID_USB_INTERFACE_NUM=01 E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: KEYBOARD_KEY_90001=chat E: KEYBOARD_KEY_90002=camera E: KEYBOARD_KEY_90003=prog1 E: KEYBOARD_KEY_90004=shop E: KEYBOARD_KEY_C0194=file E: KEYBOARD_KEY_C01A7=documents E: KEYBOARD_KEY_C01B6=images E: KEYBOARD_KEY_C01B7=sound E: KEYBOARD_KEY_C0201=new E: KEYBOARD_KEY_C0207=save E: KEYBOARD_KEY_C0208=print E: KEYBOARD_KEY_C021A=undo E: KEYBOARD_KEY_C0279=redo E: KEYBOARD_KEY_C0289=reply E: KEYBOARD_KEY_C028B=forwardmail E: KEYBOARD_KEY_C028C=send E: LIBINPUT_DEVICE_GROUP=usb-0000:00:13.2-4 E: MAJOR=13 E: MINOR=70 E: SUBSYSTEM=input E: USEC_INITIALIZED=28443463
> Seems it should use EVIOCSKEYCODE only for event5 but not event6 I meant other way, for /dev/input/event6 but not for /dev/input/event5
Closing all stale bugs with NEEDINFO. Please open a new bug at https://github.com/systemd/issues if the problem still occurs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.