Pad detection from event node path may find the wrong device.
On older kernels and wacom.ko modules, the driver may choose to group pad/stylus functionality into a single event node, which is later split by the X11 wacom driver into multiple X devices.
This possibility of having multiple X11 devices sharing the same event node path may come out wrong in the implementation of the org.gnome.Shell.Wacom.PadOsd interface though, because looking up by event node path we may come up with a device that is not the pad, and later reject it because it's not a pad.
Instead, it should be checking device type and event node path at the same time, and bail out if no matching device is found.