Your message dated Thu, 01 May 2025 14:35:16 +0200 (CEST)
with message-id <20250501123516.98788be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #946437,
regarding systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code
0x70068, and key code 110: Invalid argument
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
946437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 244-3
Severity: minor
I've noticed the following error (in red) in the journalctl output:
Dec 09 00:10:18 zira systemd-udevd[506]: event4: Failed to call EVIOCSKEYCODE
with scan code 0x70068, and key code 110: Invalid argument
This is not new.
I have a file /etc/udev/hwdb.d/98-apple-keyboard.hwdb with:
evdev:input:b0003v05ACp0221*
KEYBOARD_KEY_70068=insert # F13: Insert
and this corresponds to
Bus 002 Device 005: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
I use the F13 key for Insert, as there is no Insert key on this
keyboard (this is a Fn key at the usual place of the Insert key
and the driver honors this specificity).
I have not seen any side effect of this error, though.
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages udev depends on:
ii adduser 3.118
ii dpkg 1.19.7
ii libacl1 2.2.53-5
ii libblkid1 2.34-0.1
ii libc6 2.29-5
ii libkmod2 26-3
ii libselinux1 2.9-3+b1
ii libudev1 244-3
ii systemd-sysv 244-3
ii util-linux 2.34-0.1
udev recommends no packages.
udev suggests no packages.
Versions of packages udev is related to:
ii systemd 244-3
-- debconf information:
udev/title/upgrade:
udev/new_kernel_needed: false
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
