After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756971 - Wacom calibration window is unresponsive when trying to calibrate Cintiq 24HD
Wacom calibration window is unresponsive when trying to calibrate Cintiq 24HD
Status: RESOLVED DUPLICATE of bug 747951
Product: gnome-control-center
Classification: Core
Component: Wacom
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Carlos Garnacho
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-22 14:33 UTC by Jonathan Moerman
Modified: 2015-10-22 15:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gnome-control-center -v wacom output (2.93 KB, text/plain)
2015-10-22 14:33 UTC, Jonathan Moerman 		Details

Description Jonathan Moerman 2015-10-22 14:33:53 UTC 
Created attachment 313864 [details]
gnome-control-center -v wacom output

First reported here: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1503718

I am not able to calibrate my Wacom Cintiq 24HD in GNOME 3.16.
When I click on calibrate the calibration window fills the screen of the Cintiq and the circle in the middle of the screen slowly fills, the window does not respond to any user inputs (including keyboard inputs such as escape or alt-f4), tapping the calibration point does nothing and alt-f4 brings up a 'Wacom-tablet' is not responding window in Ubuntu 15.10.

When launching gnome-control-center with -v it becomes clear that it is ignoring my pen.

gnome-control-center does not crash and gdb doesn't give any useful information.

This bug is reproducible in both Ubuntu 15.10 (installed, updated) and fedora 22 (live usb).
Comment 1 Bastien Nocera 2015-10-22 15:11:58 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 747951 ***