systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

Bug #1406952 reported by G.Araucaria on 2015-01-01
64
This bug affects 13 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

during boot systemd-udevd reports: "Error calling EVIOCSKEYCODE: Invalid argument"

error message has been noted during boot and collected via dmesg. No device name associated with it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: systemd-services 204-5ubuntu20.9
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Jan 1 17:16:55 2015
InstallationDate: Installed on 2013-05-01 (609 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

G.Araucaria (crazy-czap) wrote :
Martin Pitt (pitti) wrote :

Can you please do

  udevadm info --export-db > /tmp/udev.txt

and attach /tmp/udev.txt here? That should give me a first clue what system you have and which keymap it is trying to set in the kernel.

Changed in systemd (Ubuntu):
status: New → Incomplete
G.Araucaria (crazy-czap) wrote :

attachment as requested

Changed in systemd (Ubuntu):
status: Incomplete → New
status: New → Incomplete
mark wade (markwade) wrote :

I've completely emptied /lib/udev/hwdb.d/60-keyboard.hwdb and still get boot errors of the sort:

systemd-udevd[285]: Error calling EVIOCSKEYCODE: Invalid argument

Each time I edited 60-keyboard.hwdb the error would go away next boot and some number of successive boots but would return with a different line number until the line numbers cited didn't even exist, all the way to an empty file.

It seems merely touching 60-keyboard.hwdb fixes the error for a bit, though I'll have to wait for the next error to confirm that.

mark wade (markwade) wrote :

I neglected to say I've restored the original /lib/udev/hwdb.d/60-keyboard.hwdb with all its entries intact and have rebooted a few times with no errors. Next error I'll touch the file and reboot and see.

G.Araucaria (crazy-czap) on 2015-01-10
Changed in systemd (Ubuntu):
status: Incomplete → New
G.Araucaria (crazy-czap) wrote :

problem apparently gone: i will close this issue

G.Araucaria (crazy-czap) wrote :

i mean i would like to close it, but i can't :(

mark wade (markwade) wrote :

Maybe I'm not supposed to post here? But since I did I'll finish up.

It seems to come and go on it's own now requiring no action from me, mostly it's gone. The last was January 12 with:

systemd-udevd[287]: Error calling EVIOCSKEYCODE: Invalid argument

but successive boots yield no further errors of this type or entries in dmesg

<shrug>

mark wade (markwade) wrote :

Last three boots yielded:

1st boot: systemd-udevd[283]: Error calling EVIOCSKEYCODE: Invalid argument
2nd boot: systemd-udevd[295]: Error calling EVIOCSKEYCODE: Invalid argument
3rd boot: systemd-udevd[287]: Error calling EVIOCSKEYCODE: Invalid argument

touching the file did not prevent a consequent error.

annoying and lengthens boot time.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Thomas Mayer (thomas303) wrote :

This bug still affects me on 14.04.2, using Kernel 3.16.0-31-generic using the original /lib/udev/hwdb.d/60-keyboard.hwdb provided by ubuntu and ubuntu updates

Peleg (freepeleg) wrote :

This bug still affects me on 14.04.2, using Kernel 3.16.0-37-generic.

I have not manually modified /lib/udev/hwdb.d/60-keyboard.hwdb, but I am not sure it is the original.

utom (utom) wrote :

This bug still affects me on 14.04.1, using Kernel 3.19.0-30-generic.

I have not manually modified /lib/udev/hwdb.d/60-keyboard.hwdb, but I am not sure it is the original.

[Appeared after nVidia drivers installation.]

Eero Aaltonen (ejn) wrote :

Also appeared after nVidia drivers installation.

I am receiving the same error on Xenial. Please let me know if I need to post more information to help debugging this error.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers