Created attachment 123398 [details] command lines and their output for my distro, and various device profiling and some logs I'm getting the below "PreInit returned 2" error when I plugin my keyboard (showing up as "Gaming Keyboard". FWIW I don't think there's anything special about the keyboard; this is the device: http://amzn.com/B00T1P6F1S): May 1 18:01:39 carboy /usr/lib/gdm3/gdm-x-session[1504]: (II) failed to create input device '/dev/input/event7'. May 1 18:01:39 carboy /usr/lib/gdm3/gdm-x-session[1504]: (EE) libinput: Gaming Keyboard: Failed to create a device for /dev/input/event7 May 1 18:01:39 carboy /usr/lib/gdm3/gdm-x-session[1504]: (EE) PreInit returned 2 for "Gaming Keyboard" May 1 18:01:39 carboy /usr/lib/gdm3/gdm-x-session[1504]: (II) UnloadModule: "libinput" (a more full /var/log/syslog output is attached, from time I plugged in the keyboard) :: Debugging/system specific info: My output from `xinput list` `lsusb` before and after plugging in (with a `tail -f /var/log/syslog` in between): attached as "SystemInfo_kernel_distro_xinput-list_lsusb_logs.txt" Pasting inline, installed packages and their versions (just `grep`ed for '(xinput|wayland|libinput)'): i A libinput10 - input device management and event handling Version: 1.2.4-1 i A libva-wayland1 - Video Acceleration (VA) API for Linux -- W Version: 1.7.0-1 i A libwayland-client0 - wayland compositor infrastructure - client Version: 1.10.0-2 i A libwayland-cursor0 - wayland compositor infrastructure - cursor Version: 1.10.0-2 i A libwayland-egl1-mesa - implementation of the Wayland EGL platform Version: 11.1.3-1 i A libwayland-server0 - wayland compositor infrastructure - server Version: 1.10.0-2 i xinput - Runtime configuration and test of XInput d Version: 1.6.2-1 i xserver-xorg-input-libinput - X.Org X server -- libinput input driver Version: 0.18.0-1 i A xwayland - Xwayland X server Version: 2:1.18.3-1 Let me know how I can further debug this. I take it from these https://wayland.freedesktop.org/libinput/doc/latest/reporting_bugs.html instructions that `evemu` doesn't apply here, since I don't have an event node that hangs around to begin with.
attach the output from evemu-describe for this device please. if it has multiple event nodes attach all of them separately please, thanks.
I can't reproduce this today (even though this was happening across reboots when I reported it). Sorry for the noise. :|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.