Created attachment 114654 [details] Xorg log on x86_64 installation Xorg crashes when a Razer Blackwidow keyboard is plugged in (part of Xorg log is appended). Arch Linux x86_64 Linux 3.19.2 libinput 0.13.0 Xorg server 1.17.1 The problem occurred after updating libinput from 0.12.0 to 0.13.0 and is only present when the named keyboard is plugged in. I tested the same setup(same software version and keyboard) on a x86 installation and it worked fine there.
I also have the same problem with libinput 0.13.0 but with my razer deathadder chroma mouse.
Created attachment 114689 [details] Xorg log showing crash: Razer Deathadder Chroma
This is happening to me as-well with a Razer Blackwidow keyboard on version 0.8.0, so it is not exclusive to 0.13.0. Wonder if this actually extends to Wayland as well or not.
Also I added the relevant part of a log to pastebin. http://pastebin.com/vdLLLLsJ
Same problem here. After updating from 0.12 to 0.13, xorg crashes when plugging in a Razer Black Widow Ultimate.
Created attachment 114767 [details] Xorg log of crash when plugging in Razer Black Widow ultimate
The crash is reproducible with wayland ( weston and GNOME ).
I bisected the issue down to commit 1e4116beb9863ecb69253b159af1f6909354600a 'evdev: refactor fake resolution setting'
(In reply to rabcor from comment #3) > This is happening to me as-well with a Razer Blackwidow keyboard on version > 0.8.0, so it is not exclusive to 0.13.0. > > Wonder if this actually extends to Wayland as well or not. I made a mistake earlier, it was xf86-input-libinput that was version 0.8.0 libinput itself is 0.13.0. Nevermind.
Please attach an evemu-describe of this device, thanks.
Created attachment 114909 [details] evemu-describe output for Razer Blackwidow 2013 attached an evemu-describe of a Razer Blackwidow 2013
Is there a second device? this one doesn't have any axes, so it's unlikely to even trigger the code that changed with the commit listed above.
Created attachment 114910 [details] evemu-describe output Razer Blackwidow - secode device There are 4 devices in total: three event and 1 mouse. names as listed under /dev/input/by-id: usb-Razer_Razer_BlackWidow_2013-event-kbd (evemu-desc I posted before) usb-Razer_Razer_BlackWidow_2013-if01-event-kbd (this comments evemu-desc) usb-Razer_Razer_BlackWidow_2013-if02-event-mouse usb-Razer_Razer_BlackWidow_2013-if02-mouse Are you interested in evemu-desc of the other two devices as well?
attach them here anyway, it's good for me to have them for future reference. The second one you attached is the one triggering the bug - fix for that is coming up.
http://lists.freedesktop.org/archives/wayland-devel/2015-April/021111.html First two patches, the rest are related but not required
Created attachment 114949 [details] evemu-describe output Razer Blackwidow 2013 if02 event mouse I added the evemu-describe for the third event device. For the fourth device (usb-Razer_Razer_BlackWidow_2013-if02-mouse) no evemu-describe can be generated (device is mouse device linked to /dev/input/mouse1). I applied your patches and 0.13.0 now works for me with the keyboard plugged in. Thanks! For anybody using Arch: I uploaded a modified libinput package here: https://kevin-maeder.de/libinput/
commit 67208c0b1acd7b6db8a853994f7e7c9be94e0178 Author: Peter Hutterer <peter.hutterer@who-t.net> Date: Wed Apr 8 09:54:29 2015 +1000 evdev: fix crash for missing ABS_X/Y commit e2b13e602220a906584b21d51bc5472577be4372 Author: Peter Hutterer <peter.hutterer@who-t.net> Date: Wed Apr 8 09:54:30 2015 +1000 evdev: fix handling of fake MT devices without ABS_X/Y
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.