Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #71267 > unrolled thread

Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument Salvatore Bonaccorso <carnil@debian.org> - 2021-05-08 15:00 +0200
    Processed: Re: Bug#946437: systemd-udevd: event4: Failed to call  EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-08 15:20 +0200
    Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument Vincent Lefevre <vincent@vinc17.net> - 2021-05-08 18:10 +0200
      Processed: Re: Bug#946437: systemd-udevd: event4: Failed to call  EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-08 18:20 +0200

#71267 — Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

Control: tags -1 + moreinfo

Hi Vincent,

On Tue, Jan 28, 2020 at 03:40:03AM +0100, Vincent Lefevre wrote:
> On 2019-12-09 00:31:29 +0100, Vincent Lefevre wrote:
> > 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.
> 
> According to the Xorg log[*], the keyboard uses 2 event devices
> (in particular, due to that, I get many duplicate lines in this
> log file: one for each event device). But the error I get in the
> journalctl output is only for the second event device.
> 
> [*] The lines from /var/log/Xorg.0.log corresponding to these two
> event devices:
> 
> [    18.667] (II) config/udev: Adding input device Apple, Inc Apple Keyboard (/dev/input/event3)
> [    18.667] (**) Option "Device" "/dev/input/event3"
> [    18.669] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [    18.669] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
> [    18.669] (II) event3  - Apple, Inc Apple Keyboard: device removed
> [    18.698] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6.2/2-6.2:1.0/0003:05AC:0221.0001/input/input9/event3"
> [    18.700] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [    18.700] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
> [    18.701] (II) config/udev: Adding input device Apple, Inc Apple Keyboard (/dev/input/event4)
> [    18.701] (**) Option "Device" "/dev/input/event4"
> [    18.704] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [    18.704] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
> [    18.704] (II) event4  - Apple, Inc Apple Keyboard: device removed
> [    18.734] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6.2/2-6.2:1.1/0003:05AC:0221.0002/input/input10/event4"
> [    18.736] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [    18.736] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
> [ 16244.494] (II) event3  - Apple, Inc Apple Keyboard: device removed
> [ 16244.510] (II) event4  - Apple, Inc Apple Keyboard: device removed
> [ 25897.048] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [ 25897.048] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
> [ 25897.049] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [ 25897.049] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
> [ 26635.074] (II) event3  - Apple, Inc Apple Keyboard: device removed
> [ 26635.094] (II) event4  - Apple, Inc Apple Keyboard: device removed
> [ 28690.158] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [ 28690.158] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
> [ 28690.159] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: Keyboard
> [ 28690.159] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard

Vincent, is this still something you are able to reproduce with a
recent kernel? If not, should we close the bug? If yes, any more
insights since the last report?

Regards,
Salvatore

[toc] | [next] | [standalone]

#71269 — Processed: Re: Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

Processing control commands:

> tags -1 + moreinfo
Bug #946437 [src:linux] systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument
Ignoring request to alter tags of bug #946437 to the same tags previously set

-- 
946437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946437
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#71308

Control: found -1 5.10.24-1

On 2021-05-08 14:53:13 +0200, Salvatore Bonaccorso wrote:
> Vincent, is this still something you are able to reproduce with a
> recent kernel? If not, should we close the bug? If yes, any more
> insights since the last report?

I still get the error in the logs due to the F13 key.
Last tested with:

Linux version 5.10.0-5-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.24-1 (2021-03-19)

-- 
Vincent Lefèvre <vincent@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)

[toc] | [prev] | [next] | [standalone]

#71310 — Processed: Re: Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

Processing control commands:

> found -1 5.10.24-1
Bug #946437 [src:linux] systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument
Marked as found in versions linux/5.10.24-1.

-- 
946437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946437
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web