Arch Linux

vityafx

Member

Registered: 2015-11-01

Posts: 40

A udev/libinput concurrency

I have just checked my Xorg.0.log log file and found this:

[   511.705] (II) config/udev: Adding input device Kingsis Peripherals ZOWIE Gaming mouse (/dev/input/event22)
[   511.705] (**) Kingsis Peripherals ZOWIE Gaming mouse: Applying InputClass "libinput pointer catchall"
[   511.705] (**) Kingsis Peripherals ZOWIE Gaming mouse: Applying InputClass "FX libinput Mouse Profile"
[   511.705] (II) Using input driver 'libinput' for 'Kingsis Peripherals ZOWIE Gaming mouse'
[   511.761] (II) systemd-logind: got fd for /dev/input/event22 13:86 fd 41 paused 0
[   511.761] (**) Kingsis Peripherals ZOWIE Gaming mouse: always reports core events
[   511.761] (**) Option "Device" "/dev/input/event22"
[   511.761] (**) Option "_source" "server/udev"
[   511.765] (II) event22 - Kingsis Peripherals ZOWIE Gaming mouse: is tagged by udev as: Mouse
[   511.766] (II) event22 - Kingsis Peripherals ZOWIE Gaming mouse: device is a pointer
[   511.766] (II) event22 - Kingsis Peripherals ZOWIE Gaming mouse: device removed
[   511.766] (**) Option "AccelSpeed" "0"
[   511.766] (**) Option "AccelProfile" "flat"
[   511.766] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1AF3:0001.0006/input/input22/event22"
[   511.766] (II) XINPUT: Adding extended input device "Kingsis Peripherals ZOWIE Gaming mouse" (type: MOUSE, id 13)
[   511.767] (**) Option "AccelerationScheme" "none"
[   511.767] (**) Kingsis Peripherals ZOWIE Gaming mouse: (accel) selected scheme none/0
[   511.767] (**) Kingsis Peripherals ZOWIE Gaming mouse: (accel) acceleration factor: 2.000
[   511.767] (**) Kingsis Peripherals ZOWIE Gaming mouse: (accel) acceleration threshold: 4
[   511.770] (II) event22 - Kingsis Peripherals ZOWIE Gaming mouse: is tagged by udev as: Mouse
[   511.771] (II) event22 - Kingsis Peripherals ZOWIE Gaming mouse: device is a pointer
[   511.773] (II) config/udev: Adding input device Kingsis Peripherals ZOWIE Gaming mouse (/dev/input/mouse1)
[   511.773] (**) Kingsis Peripherals ZOWIE Gaming mouse: Applying InputClass "FX libinput Mouse Profile"
[   511.773] (II) Using input driver 'libinput' for 'Kingsis Peripherals ZOWIE Gaming mouse'
[   511.773] (**) Kingsis Peripherals ZOWIE Gaming mouse: always reports core events
[   511.773] (**) Option "Device" "/dev/input/mouse1"
[   511.773] (**) Option "_source" "server/udev"
[   511.837] (II) mouse1  - failed to create input device '/dev/input/mouse1'.
[   511.837] (EE) libinput: Kingsis Peripherals ZOWIE Gaming mouse: Failed to create a device for /dev/input/mouse1
[   511.837] (EE) PreInit returned 2 for "Kingsis Peripherals ZOWIE Gaming mouse"
[   511.837] (II) UnloadModule: "libinput"

It seems that udev first creates the device `/dev/input/mouse1` for my mouse and then libinput tries to do the same and fails. I wonder, does it affect any settings I use for the mouse? Is this actually a problem?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,232

Re: A udev/libinput concurrency

udev creates the device node for /dev/input/mouse1, libinput reacts to that event and tries to create a logical xorg device for the just announced /dev/input/mouse1 node. This doesn't look like a race condition between the two but rather a device being announced that libinput can't do much with. if you don't notice anything off I'd say don't worry too much about it.

In my log it simply ignores that device as the other event* definition is what actually holds the relevant information.

Do you have a nvidia-xconfig generated xorg.config ? That will be the issue as it loads unnecessary legacy mouse drivers that aren't really relevant anymore.

vityafx

Member

Registered: 2015-11-01

Posts: 40

Re: A udev/libinput concurrency

udev creates the device node for /dev/input/mouse1, libinput reacts to that event and tries to create a logical xorg device for the just announced /dev/input/mouse1 node. This doesn't look like a race condition between the two but rather a device being announced that libinput can't do much with. if you don't notice anything off I'd say don't worry too much about it.

In my log it simply ignores that device as the other event* definition is what actually holds the relevant information.

Do you have a nvidia-xconfig generated xorg.config ? That will be the issue as it loads unnecessary legacy mouse drivers that aren't really relevant anymore.

Yes, indeed, I am using nvidia configuration. There are two sections for the input devices from my xorg.conf:

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Shall I/Can I just remove these two? It also seems odd to me as, in my opinion, we should not have two different drivers used for the same devices (keyboard and mouse in this case)...

UPD:

I've just tried commenting these two sections out, and also the references to those in the serverlayout section:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    #InputDevice    "Keyboard0" "CoreKeyboard"
    #InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Everything seems to work just fine, but the xorg.0.log is exactly the same as in my first post here.

Last edited by vityafx (2020-06-10 09:25:16)