This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1890186
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 linux package in Ubuntu:
Incomplete
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/linux/+bug/1890186/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
