The logic that libinput uses to determine if two devices should be part of the same group winds up grouping together anything behind the same USB hub. The Cintiq 24HDT uses such a hub internally to provide seperate tablet and touchscreen devices. It also, however, exposes one of the hub's ports externally for the user to connect things to. If another input device is connected to that port, it will be added to the same group as the Cintiq. This can also be observed with /any/ USB hub, grouping all devices plugged into it. This doesn't seem to cause any issues at the moment, but has been filed so it isn't forgotten. I imagine that fixing it will likely first require having libwacom or udev provide more information about related devices.
Can you attach a udevadm info --export-db from such a device tree please. So we have it available when we get to it. thanks.
Created attachment 114925 [details] Output from `udevadm info --export-db` Here's the requested output. Both an Intuos (056a:0303) and Intuos Pro (056a:0315) are connected behind a generic USB hub (1a40:0201). The output from libinput's event-debug tool starts off with: event2 DEVICE_ADDED Power Button seat0 default group1 cap:k event1 DEVICE_ADDED Power Button seat0 default group2 cap:k event19 DEVICE_ADDED Wacom Intuos PT M Pen seat0 default group3 cap:T size 216.00/135.00mm left event20 DEVICE_ADDED Wacom Intuos PT M Finger seat0 default group3 cap:p size 215.58/136.53mm tap left scroll-nat scroll-2fg-edge event16 DEVICE_ADDED Wacom Intuos Pro M Pen seat0 default group3 cap:T size 223.52/139.70mm left event18 DEVICE_ADDED Wacom Intuos Pro M Finger seat0 default group3 cap:p size 227.56/141.24mm tap left scroll-nat scroll-2fg-edge event0 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group4 cap:k event4 DEVICE_ADDED Dell WMI hotkeys seat0 default group5 cap:k
Created attachment 114975 [details] [review] 0001-udev-prepend-the-libinput-group-with-the-product-str.patch simple fix, likely going to be enough for what we need though, right? I'm not sure there is an easy generic fix to the "I've plugged a 24HD into a 24HD" case. Though that use case suggests you have enough money to get someone to write a custom udev rule for you ;)
I think the intent of Benjamin's Yeah, that should do the trick as least as far as this bug is concerned. Even ignoring the 24HD-connected-to-a-24HD case, this patch won't work right on a 24HD (or any Wacom pen & touch display tablet IIRC) since the pen and touch devices have separate USB PIDs. Though, unless you have some other means of knowing the PID of the associated device, I think you're pretty much out of luck trying to simply detect it.
damn, something was at the back of my head when I wrote this telling me I've seen different pids for the same device before. Back to the drawing board I guess.
http://lists.freedesktop.org/archives/wayland-devel/2015-June/022797.html patch from above with a different commit message. doesn't solve the issue here, but solves the issue with misc devices plugged into the same usb hub
commit b1fc392268807653956867867dba3fdfabfc4d05 Author: Peter Hutterer <peter.hutterer@who-t.net> Date: Thu Apr 9 16:08:14 2015 +1000 udev: prepend the libinput group with the product string
I'm going to close this one as fixed. It fixes part of the problem, albeit not the originally reported one for the 24HD. Can't come up with a better solution, the best option here is to have local configuration that assigns the libinput device group manually.
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.