control-center, wacom-tablet: Calibration window is unresponsive

[Jonathan Moerman]

I am not able to calibrate my Wacom Cintiq 24HD in Ubuntu Gnome 15.10 (Beta 1, fresh install).
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, tapping the calibration point does nothing and alt-f4 brings up a 'Wacom-tablet' is not responding window.

This bug will always occur when trying to calibrate my Cintiq.
I have reproduced this bug 10+ times with both the nvidia binary driver and nouveau driver.
gnome-control-center will not crash, it has a cpu usage of 0,0% according to top and it does not give any usefull output when launched from the terminal or gdb.

Version of:
 - gnome-control-center: 1:3.16.2ubuntu3
 - Linux: 4.2.0-14-generic x86_64
 - Xorg 1:7.7+7ubuntu4

Although this bug renders this installation useless for me I will leave it installed for a while, in case anyone needs me to test a fix.
---
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2015-10-05 (2 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150826.1)
NonfreeKernelModules: nvidia
Package: gnome-control-center 1:3.16.2-2ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Tags: wily
Uname: Linux 4.2.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Jonathan Moerman (jonathanmoerman)]

Oh, it may also be useful to know that the Cintiq itself works just fine in applications like gimp, and mapping buttons also works just fine.

[Tim Lunn (darkxst)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 1503718

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Also can you run and log the output using:
gnome-control-center -v

[Jonathan Moerman (jonathanmoerman)]

apport information

[Jonathan Moerman (jonathanmoerman)]

apport information

[Jonathan Moerman (jonathanmoerman)]

Should have thought about the -v flag, that was a bit stupid...
This does answer why it isn't responding to my pen, but not why you cant close the window in any normal way after it has timed out.
Ignoring the device its meant to calibrate kinda defeats the purpose.

[Tim Lunn (darkxst)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Jonathan Moerman (jonathanmoerman)]

I haven't had enough time and energy to do this sooner, but I've reproduced the bug in fedora 22 and reported this issue upstream.

I reported it here: https://bugzilla.gnome.org/show_bug.cgi?id=756971

[Jonathan Moerman (jonathanmoerman)]

A workaround has been reported here: https://bugzilla.gnome.org/show_bug.cgi?id=747951#c1

Executing "export CLUTTER_BACKEND=x11 && gnome-control-center wacom" allowed me to calibrate my Cintiq.

[Bastian Lembke (cakewhisperer)]

Hi

I had the same problem. Couldn't assign my Wacom Intous 5 express keys. I found a solution online. I changed in the d-conf editor "org.gnome.settings-daemon.plugins.gsdwacom" the priority from 0 to 20. That fixed it for me after a reboot.

Hope this is helpful.

[Jonathan Moerman (jonathanmoerman)]

Configuring keys wasn't a problem, you probably encountered a different bug.