This bug is very old, and I do not see it any longer on a newer Dell
laptop and a newer Ubuntu release.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1597415
Title:
systemd-udevd: Error calling
** Tags added: disco eoan
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9'
** Tags added: cscc
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9' (scan
Seeing the same error on Dell Latitude e6520 on 18.04.2 LTS, 4.15.0-45
kernel
Not sure if it has any detrimental effects though
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Confirming the same issue on Ubuntu Server 18.04 LTS:
Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code
0x9004c, key code 162): Invalid argument
CODE_FILE ../src/udev/udev-builtin-keyboard.c
CODE_FUNC map_keycode
CODE_LINE 103
ERRNO 22
PRIORITY
Problem occured when force shutdown windows and booted up ubuntu. I was
able to bypass this bug by commenting out windows partition mount in
fstab
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on
device node '/dev/input/event3' (scan code 0x90001, key code 148): Invalid
argument
Mär 19 14:50:58 stefano-PC systemd-udevd[458]: Error calling EVIOCSKEYCODE on
device node '/dev/input/event3' (scan code 0x90002, key
Can confirm this bug in Ubuntu 17.04 with kernel 4.10.0-13-generic.
--
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/1597415
Title:
systemd-udevd: Error calling
I am still seeing this error with the 4.10.1-041001-generic mainline
kernel.
--
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/1597415
Title:
systemd-udevd: Error calling
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-17.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Fix on comment #7 worked for me on a Dell Latitude 3150,
4.8.0-36-generic kernel.
Thanks!
--
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/1597415
Title:
systemd-udevd:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE
This bug definitely depends on kernel version. Both the fix mentioned
above in #8
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/comments/8
and mainline kernel after this commit (found with reverse bisect), are
required. Marking as linux bug. Would be very nice if fix could make it
I tested with a 4.9.2 mainline kernel.
I will try to test with an Ubuntu kernel when I have a chance to reboot my
system...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Fix may be dependent on kernel version; testing with stock kernel for
Ubuntu 16.04, v4.4, results in:
Jan 10 19:32:33 Bethany systemd-udevd[332]: Error calling EVIOCSKEYCODE
on device node '/dev/input/event11' (scan code 0x100150, key code 190):
Invalid argument
Previous testing used kernel v4.9
On my Dell Latitude E6520 with Ubuntu 16.10, after applying the
"KEYBOARD_KEY_150=f20" -> "KEYBOARD_KEY_100150=f20" patch, I get this
error:
janv. 10 14:13:24 vougeot systemd-udevd[954]: Error calling
EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x100150,
key code 190): Invalid
This fix doesn't work for me (Dell Latitude E6540, Ubuntu 16.04);
/var/log/syslog mentions instead:
Error calling EVIOCSKEYCODE on device node '/dev/input/event17' (scan
code 0x100150, key code 190): Invalid argument
--
You received this bug notification because you are a member of Ubuntu
Touch
https://github.com/systemd/systemd/pull/5012
Change "KEYBOARD_KEY_150=f20" to "KEYBOARD_KEY_100150=f20" should fix
this issue.
Confirming this fix works here.
Editing /lib/udev/hwdb.d/60-keyboard.hwdb with the change above followed by
:~$ udevadm hwdb --update
~:$ udevadm trigger
Enables mic
** Tags added: yakkety zesty
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9'
https://github.com/systemd/systemd/pull/5012
Change "KEYBOARD_KEY_150=f20" to "KEYBOARD_KEY_100150=f20" should fix
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I have the same on Dell Latitude 7370 on Zesty daily iso & 16.04.
Marking my other report as a duplicate of this one.
--
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/1597415
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
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/1597415
Title:
systemd-udevd: Error calling
confirmed on Dell Latitude E7440
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
In /lib/udev/hwdb.d/60-keyboard.hwdb I see the following related to scan
code 150:
# Dell Latitude microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*
# Dell Precision microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*
I have exactly the same message for my Dell Latitude E6540.
--
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/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on
27 matches
Mail list logo
