On 04/26/16 09:36, Julien Cristau wrote: > No it's not... You can still configure things in xorg.conf, replace > InputDevice with InputClass, remove the "driver", "device" and "dev > name" lines, and you can use MatchUSBID or MatchProduct/MatchVendor to > select the device. xinput can't do that on the client side. >
xinput can, using the ambiguous device id. But since its ambiguous it is not very useful. What do I have to do to get this fixed?