Ok here's my understanding of this:
Most keyboards report a single usb device 'interface' for the keyboard
(some have separate interface(s) for builtin mice or other non-keyboard
stuff). However, your keyboard reports two separate 'interfaces' for
your single keyboard. Unfortunately, both of the interfaces it reports
use the exact same vendor and product id, so there's no way for systemd
to tell which is which, from the bus/vendor/product info.
The setting in the hwdb matches specifically on this bus/vendor/product id info
(the b0003v045Ep00DB string):
evdev:input:b0003v045Ep00DB*
This applies the scancode remapping to *both* of the interfaces that
your keyboard reports. However, only one of the interfaces actually
supports the remapped scancodes, so when systemd attempts to tell the
kernel to map the specific scancode to the assigned keycode, the kernel
rejects it, which results in the warning messages you saw in the logs.
However these warning log messages are only produced for the second
interface which doesn't actually support or provide the scancodes in
question. So, this logged warning is completely harmless and you can
ignore it.
It's possible that we might be able to figure out how to finesse systemd
hwdb config to get around the fact that your hardware keyboard is
essentially broken (because it reports two separate interfaces with
identical vendor/product ids but with different operation and behavior).
However since these logged errors are completely harmless, and any 'fix'
could possibly (accidentally) cause the mapped keys to *not* function, I
don't think it's worth it to bother fixing this.
Therefore I'm going to close this as wontfix, since I believe this is a
hardware problem that does not have any actual impact on the system's
operation, besides logging a harmless warning message.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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 linux package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Won't Fix
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/linux/+bug/1890186/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
