GNOME Bugzilla – Bug 747951
Tablet calibration targets do not respond to clicks
Last modified: 2015-10-22 15:11:58 UTC
The targets in the Wacom panel's calibration tool no longer respond to clicks from the appropriate stylus. This occurs because the device ID which is provided to the calibration tool by 'cc-wacom-page.c:run_calibration' is not equal to the device ID that is seen when the button is pressed.
Further investigation shows that the Wacom panel uses the "device-id" property that is present on GdkDevice objects which originate from the XI2 backend, while clutter doesn't peek at this property and instead creates its own device IDs by incrementing a counter as it becomes aware of GdkDevice objects. As a workaround, "CLUTTER_BACKEND=x11" can be set in the environment prior to running gnome-control-center. With this set, the clutter devices will have the same XI2 device IDs that are present in the "device-id" property.
The device-id property is a XI2 property only, so if Clutter were to use it in the GDK backend we'd have to handle it specially, not through generic code.
Created attachment 302149 [details] [review] gdk/device: Propagate more device details from GDK In order to do device matching we need to propagate more information, like the device_id (only on X11 with the XInput2 extension enabled), the vendor id, and the product id.
Created attachment 302150 [details] [review] gdk/device: Propagate more device details from GDK / v2 In order to do device matching we need to propagate more information, like the device_id (only on X11 with the XInput2 extension enabled), the vendor id, and the product id. Changes from v1: - Avoid run time warnings with master devices
Re-assigning to Clutter.
*** Bug 747880 has been marked as a duplicate of this bug. ***
Pushed attachment 302150 [details] [review] to master, but more testing is appreciated.
I was finally able to get my jhbuild instance of GNOME updated and running. I can confirm that this seems to have done the trick: the targets now respond to clicks when using either the x11 or gdk backend. Thanks!
*** Bug 756971 has been marked as a duplicate of this bug. ***