[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

[Md Ayquassar]

After commenting the corresponding lines /lib/udev/hwdb.d/60-keyboard.hwdb out, issuing
# systemd-hwdb update
and rebooting, the middle slider up/down keys stopped producing any effect completely at least in Firefox (i.e., it got worse). The "Failed to call ..." error is gone from the output of journalctl -b, though.  Running evtest and checking event8 produces absolutely no effect for the slider keys. Running evtest and checking event9 produces the following effect for the slider keys up (+) followed by down (-):
Event: time 1597336850.366186, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d
Event: time 1597336850.366186, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 1
Event: time 1597336850.366186, -------------- SYN_REPORT ------------
Event: time 1597336850.510185, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d
Event: time 1597336850.510185, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 0
Event: time 1597336850.510185, -------------- SYN_REPORT ------------
Event: time 1597336851.454182, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e
Event: time 1597336851.454182, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 1
Event: time 1597336851.454182, -------------- SYN_REPORT ------------
Event: time 1597336851.526184, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e
Event: time 1597336851.526184, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 0
Event: time 1597336851.526184, -------------- SYN_REPORT ------------

I'll revert to the prior default setting of
/lib/udev/hwdb.d/60-keyboard.hwdb in the meantime.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186

Title:
  Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103:
  Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel
  5.4.0-42-generic on Dell Latitude E6440.  Upon examining the output of
  journalctl -b, I see this:

  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288
  Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

  "Invalid argument" means that something goes wrong there, and I don't know what it is.
  On my laptop, event8 seems to be keyboard-related:

  $ sudo cat /proc/bus/input/devices | grep -C 5 event8
  I: Bus=0003 Vendor=045e Product=00db Version=0111
  N: Name="Microsoft Natural® Ergonomic Keyboard 4000"
  P: Phys=usb-0000:00:14.0-13.1/input0
  S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event8 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe
  B: MSC=10
  B: LED=107

  The issue report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is
  probably related but marked as a duplicate of a no longer existing
  issue report (#1750855).

  The report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415
  describes a similar issue for older kernels; the differences pertain
  to error message, error code, input..., and, opposed to #19 there, I
  have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine
  is not a dual-boot machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions